Skip to content

No way to capture unhandled errors #8417

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nex3 opened this issue Feb 8, 2013 · 2 comments
Closed

No way to capture unhandled errors #8417

nex3 opened this issue Feb 8, 2013 · 2 comments
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-duplicate Closed in favor of an existing report

Comments

@nex3
Copy link
Member

nex3 commented Feb 8, 2013

This seems like the sort of thing that there'd already be a bug about, but I wasn't able to find one. Apologies if this is a duplicate.

There needs to be some way of capturing and dealing with unhandled exceptions. Currently on the VM they always take down the entire process, which (while correct as the default behavior) is very frustrating when trying to debug or write test code.

@sigmundch
Copy link
Member

Issue #8442 has been merged into this issue.


cc @jmesserly.
cc @gbracha.

@sethladd
Copy link
Contributor

sethladd commented Mar 6, 2013

Added Duplicate label.
Marked as being merged into #8875.

@nex3 nex3 added Type-Defect area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-duplicate Closed in favor of an existing report labels Mar 6, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

3 participants