Skip to content

Debugging access violation on Windows #6121

Closed
Closed
Debugging access violation on Windows#6121
Labels
questionIssues asking questions about Node.js.v8 engineIssues and PRs related to the V8 dependency.windowsIssues and PRs related to the Windows platform.

Description

@daniel-white
daniel-white
opened on Apr 8, 2016
  • 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?

Activity

  1. Fishrock123 commented on Apr 8, 2016

    @Fishrock123
    Fishrock123
    on Apr 8, 2016
    Contributor

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

  2. Fishrock123
    added
    docIssues and PRs related to Node.js documentation.
    on Apr 8, 2016

  3. daniel-white commented on Apr 8, 2016

    @daniel-white
    daniel-white
    on Apr 8, 2016
    Author

    I'll try that. Thanks!

  4. Fishrock123 commented on Apr 8, 2016

    @Fishrock123
    Fishrock123
    on Apr 8, 2016
    Contributor

    Ah, I think it is a v8 flag.

  5. Fishrock123
    added
    questionIssues asking questions about Node.js.
    v8 engineIssues and PRs related to the V8 dependency.
    and removed
    docIssues and PRs related to Node.js documentation.
    on Apr 8, 2016

  6. daniel-white commented on Apr 8, 2016

    @daniel-white
    daniel-white
    on Apr 8, 2016
    Author

    Where does it dump them to?

  7. mscdex
    added
    windowsIssues and PRs related to the Windows platform.
    on Apr 8, 2016

  8. Fishrock123 commented on Apr 8, 2016

    @Fishrock123
    Fishrock123
    on Apr 8, 2016
    Contributor

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

  9. mscdex commented on Apr 9, 2016

    @mscdex
    mscdex
    on Apr 9, 2016
    Contributor

    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.

  10. targos commented on May 30, 2017

    @targos
    targos
    on May 30, 2017
    Member

    Looks like it was answered.

  11. targos
    closed this as completedon May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionIssues asking questions about Node.js.v8 engineIssues and PRs related to the V8 dependency.windowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions