Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Debugging access violation on Windows #6121

Closed
daniel-white opened this issue Apr 8, 2016 · 7 comments
Closed

Debugging access violation on Windows #6121

daniel-white opened this issue Apr 8, 2016 · 7 comments
Labels
question Issues that look for answers. v8 engine Issues and PRs related to the V8 dependency. windows Issues and PRs related to the Windows platform.

Comments

@daniel-white
Copy link

  • Version: 4.4.1 32-bit
  • Platform: Windows
  • Subsystem:

I'm hitting a case where something is generating an exit code with "access violation". Is there a flag that I can set in a build and/or command line to force node to crash and not gracefully exit so that I can get a crash dump?
@Fishrock123
Copy link
Contributor

@daniel-white Do you mean --abort-on-uncaught-exception? (Which doesn't appear to be documented in our CLI docs for some reason...)

@Fishrock123 Fishrock123 added the doc Issues and PRs related to the documentations. label Apr 8, 2016
@daniel-white
Copy link
Author

I'll try that. Thanks!

@Fishrock123
Copy link
Contributor

Ah, I think it is a v8 flag.

@Fishrock123 Fishrock123 added question Issues that look for answers. v8 engine Issues and PRs related to the V8 dependency. and removed doc Issues and PRs related to the documentations. labels Apr 8, 2016
@daniel-white
Copy link
Author

Where does it dump them to?

@mscdex mscdex added the windows Issues and PRs related to the Windows platform. label Apr 8, 2016
@Fishrock123
Copy link
Contributor

@daniel-white On Unix, /cores/ iirc. Not sure about windows.

@mscdex
Copy link
Contributor

mscdex commented Apr 9, 2016

For Windows you might check %localappdata%\Microsoft\Windows\WER. Otherwise check the path at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps in the registry.

@gibfahn gibfahn mentioned this issue Jul 14, 2016
Closed
@targos
Copy link
Member

targos commented May 30, 2017

Looks like it was answered.

@targos targos closed this as completed May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Issues that look for answers. v8 engine Issues and PRs related to the V8 dependency. windows Issues and PRs related to the Windows platform.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mscdex @daniel-white @Fishrock123 @targos