-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Easy segmentation fault in mac node --debug #4322
Labels
util
Issues and PRs related to the built-in util module.
Comments
I get the same result on v5.3.0 and v4.2.2. |
bnoordhuis
added a commit
to bnoordhuis/io.js
that referenced
this issue
Dec 17, 2015
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: nodejs#4261 Fixes: nodejs#4322
Fishrock123
pushed a commit
to Fishrock123/node
that referenced
this issue
Dec 22, 2015
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: nodejs#4261 Fixes: nodejs#4322 PR-URL: nodejs#4328 Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fishrock123
pushed a commit
to Fishrock123/node
that referenced
this issue
Jan 6, 2016
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: nodejs#4261 Fixes: nodejs#4322 PR-URL: nodejs#4328 Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Jan 26, 2016
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: #4261 Fixes: #4322 PR-URL: #4328 Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Feb 11, 2016
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: #4261 Fixes: #4322 PR-URL: #4328 Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins
pushed a commit
to MylesBorins/node
that referenced
this issue
Feb 11, 2016
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: nodejs#4261 Fixes: nodejs#4322 PR-URL: nodejs#4328 Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins
pushed a commit
to MylesBorins/node
that referenced
this issue
Feb 15, 2016
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: nodejs#4261 Fixes: nodejs#4322 PR-URL: nodejs#4328 Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: James M Snell <[email protected]>
scovetta
pushed a commit
to scovetta/node
that referenced
this issue
Apr 2, 2016
Fix a segmentation fault when the debug message handler was called from a context without an associated `node::Environment`. Fixes: nodejs#4261 Fixes: nodejs#4322 PR-URL: nodejs#4328 Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: James M Snell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
try this v5.1.1
node --debug;
const obj = Promise.resolve(1);
util.inspect(obj)
['any command after last command']
after run util.inspect(obj), any new command will cause segmentation fault on Mac's node .
more information:
The text was updated successfully, but these errors were encountered: