镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

stepping through a three lines of code crashes node 4.2.6 #4917

Description

@weinand

launch this snippet test.js:

var obj = {};
console.log(obj);
console.log(obj);

with node --debug-brk test.js and attach a debugger, e.g. node-inspector or VSCode.

The first step command works fine, the second step crashes node on all platforms.

Activity

  1. bnoordhuis commented on Jan 27, 2016

    @bnoordhuis
    Member

    Can you check that the nightly build works? This sounds like #4261 and #4322 (and a few more) which were fixed in #4328.

  2. weinand commented on Jan 27, 2016

    @weinand
    Author

    @bnoordhuis no, the nightly build still cannot successfully step over the second console.log. The only difference I see on OS X is that I don't get an OS alert for the crashing node application. In node 4.2.6 I got an alert.

  3. bnoordhuis commented on Jan 27, 2016

    @bnoordhuis
    Member

    I cannot reproduce with master, at least not with the built-in debug client (node debug 127.0.0.1:5858). The client does hang after the second step but that's #4651, an unrelated issue. The debuggee prints {} twice, as expected.

  4. MylesBorins commented on Jan 27, 2016

    @MylesBorins
    Contributor

    This looks like a duplicate of the hug I'm working on with util and debug
    contexts. I'll add the issue number when I'm on my computer
    On Jan 27, 2016 2:23 PM, "Ben Noordhuis" notifications@github.com wrote:

    I cannot reproduce with master, at least not with the built-in debug
    client (node debug 127.0.0.1:5858). The client does hang after the second
    step but that's #4651 #4651, an
    unrelated issue. The debuggee prints {} twice, as expected.

    —
    Reply to this email directly or view it on GitHub
    #4917 (comment).

  5. bnoordhuis commented on Jan 27, 2016

    @bnoordhuis
    Member

    As a data point, when I revert commit 25776f3 (the fix from #4328), the debuggee does crash on the second step. Maybe there is more at play but for now my money is on #4328.

  6. weinand commented on Jan 27, 2016

    @weinand
    Author

    @bnoordhuis yes, the problem doesn't repro with the built-in debug client.

  7. evanlucas commented on Mar 8, 2016

    @evanlucas
    Contributor

    I cannot reproduce this on master using node-inspector. Is this still an issue?

  8. MylesBorins commented on Mar 8, 2016

    @MylesBorins
    Contributor

    I think this was fixed a while back. Closing

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions