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

node 5.5: util.format on object crahes debugger #4952

Closed
thomas-mindruptive opened this issue Jan 29, 2016 · 7 comments
Closed

node 5.5: util.format on object crahes debugger #4952

thomas-mindruptive opened this issue Jan 29, 2016 · 7 comments
Labels
util Issues and PRs related to the built-in util module.

Comments

@thomas-mindruptive
Copy link

node 5.5, windows 8.1

Following code crashes the debugger (it exits the app on "util.format" without an error message).

var util = require("util");
var obj = { 1: "fasdadsaas", 2: "safsdafdsafsadfad" };
var message = util.format("Format the object: %O", obj);
var i = 1;

Reproducible through "node debug formatBug.js", as well as node-inspector and Visual Studio Code.

For us it's quite severe because we are logging to the console extensively during development. "console.log" uses "util.format" and therefore crashes the debugger.

Thanks
mind
@mscdex mscdex added util Issues and PRs related to the built-in util module. debugger labels Jan 29, 2016
@MylesBorins
Copy link
Contributor

@mindruptive I have a patch in that should fix this although we are just trying to get a working test for it. I'm hoping I can get this working today.

#4819

@thomas-mindruptive
Copy link
Author

Thanks a lot for the fast response.
Best
mind

@thomas-mindruptive
Copy link
Author

P.S.: For the moment, I'm using following work around: I'm replacing the various "console.log" functions by my own. They simply tunnel/send the log statements to a chrome browser through web sockets. That's good enough for the moment and makes the log output easily readable.
Best
Thomas

@MylesBorins
Copy link
Contributor

The fix is now in master, you should expect this to see it in a release in the next 2 - 3 weeks on v4 and v5.

@thomas-mindruptive
Copy link
Author

thanks,
best mind

rvagg pushed a commit that referenced this issue Feb 8, 2016
@rvagg
node_contextify: do not incept debug context
1b49dfb 
Currently a debug context is created for various calls to util.

If the node debugger is being run the main context is the debug
context. In this case node_contextify was freeing the debug context
and causing everything to explode.

This change moves around the logic and no longer frees the context.

There is a concern about the dangling pointer

The regression test was adapted from code submitted by @3y3 in #4815

Fixes: #4440
Fixes: #4815
Fixes: #4597
Fixes: #4952

PR-URL: #4815

Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
rvagg pushed a commit that referenced this issue Feb 9, 2016
@rvagg
node_contextify: do not incept debug context
7003a4e 
Currently a debug context is created for various calls to util.

If the node debugger is being run the main context is the debug
context. In this case node_contextify was freeing the debug context
and causing everything to explode.

This change moves around the logic and no longer frees the context.

There is a concern about the dangling pointer

The regression test was adapted from code submitted by @3y3 in #4815

Fixes: #4440
Fixes: #4815
Fixes: #4597
Fixes: #4952

PR-URL: #4815

Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
@MylesBorins
Copy link
Contributor

The fix is now released in v5.6.0. Expect LTS next week

MylesBorins pushed a commit that referenced this issue Feb 11, 2016
node_contextify: do not incept debug context
8b08780 
Currently a debug context is created for various calls to util.

If the node debugger is being run the main context is the debug
context. In this case node_contextify was freeing the debug context
and causing everything to explode.

This change moves around the logic and no longer frees the context.

There is a concern about the dangling pointer

The regression test was adapted from code submitted by @3y3 in #4815

Fixes: #4440
Fixes: #4815
Fixes: #4597
Fixes: #4952

PR-URL: #4815

Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
MylesBorins pushed a commit to MylesBorins/node that referenced this issue Feb 11, 2016
node_contextify: do not incept debug context
e7a7c8c 
Currently a debug context is created for various calls to util.

If the node debugger is being run the main context is the debug
context. In this case node_contextify was freeing the debug context
and causing everything to explode.

This change moves around the logic and no longer frees the context.

There is a concern about the dangling pointer

The regression test was adapted from code submitted by @3y3 in nodejs#4815

Fixes: nodejs#4440
Fixes: nodejs#4815
Fixes: nodejs#4597
Fixes: nodejs#4952

PR-URL: nodejs#4815

Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
MylesBorins pushed a commit to MylesBorins/node that referenced this issue Feb 13, 2016
@MylesBorins
node_contextify: do not incept debug context
76dbef9 
Currently a debug context is created for various calls to util.

If the node debugger is being run the main context is the debug
context. In this case node_contextify was freeing the debug context
and causing everything to explode.

This change moves around the logic and no longer frees the context.

There is a concern about the dangling pointer

The regression test was adapted from code submitted by @3y3 in nodejs#4815

Fixes: nodejs#4440
Fixes: nodejs#4815
Fixes: nodejs#4597
Fixes: nodejs#4952

PR-URL: nodejs#4815

Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
MylesBorins pushed a commit to MylesBorins/node that referenced this issue Feb 15, 2016
node_contextify: do not incept debug context
1b070e4 
Currently a debug context is created for various calls to util.

If the node debugger is being run the main context is the debug
context. In this case node_contextify was freeing the debug context
and causing everything to explode.

This change moves around the logic and no longer frees the context.

There is a concern about the dangling pointer

The regression test was adapted from code submitted by @3y3 in nodejs#4815

Fixes: nodejs#4440
Fixes: nodejs#4815
Fixes: nodejs#4597
Fixes: nodejs#4952

PR-URL: nodejs#4815

Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
@MylesBorins
Copy link
Contributor

The fix is now in lts on v4.3.1 !

scovetta pushed a commit to scovetta/node that referenced this issue Apr 2, 2016
node_contextify: do not incept debug context
27eb3cf 
Currently a debug context is created for various calls to util.

If the node debugger is being run the main context is the debug
context. In this case node_contextify was freeing the debug context
and causing everything to explode.

This change moves around the logic and no longer frees the context.

There is a concern about the dangling pointer

The regression test was adapted from code submitted by @3y3 in nodejs#4815

Fixes: nodejs#4440
Fixes: nodejs#4815
Fixes: nodejs#4597
Fixes: nodejs#4952

PR-URL: nodejs#4815

Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
util Issues and PRs related to the built-in util module.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mscdex @MylesBorins @thomas-mindruptive