Skip to content

Don't print an error and exit on uncaughtException if there are other uncaughtException listeners present. #46

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
wants to merge 1 commit into from

Conversation

CrispyConductor
Copy link

Node's default behavior is to only print an exception and exit if there is no other uncaughtException handler registered. This emulates that default behavior by bypassing the uncaughtException handler if other handlers are registered.

@oppenlander
Copy link

👍

1 similar comment
@Flickdm
Copy link

Flickdm commented Mar 26, 2015

+1

@julien-f
Copy link
Collaborator

@crispy1989 Could you rebase this PR on top of the latest master?

@LinusU
Copy link
Collaborator

LinusU commented Jun 16, 2015

Also, this tests passes without the patch because of how compareLines works :(

@LinusU LinusU mentioned this pull request Jun 16, 2015
@julien-f
Copy link
Collaborator

Fixed by #77.

@julien-f julien-f closed this Jun 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants