{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/node/issues/4382","repository_url":"https://api.github.com/repos/nodejs/node","labels_url":"https://api.github.com/repos/nodejs/node/issues/4382/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/node/issues/4382/comments","events_url":"https://api.github.com/repos/nodejs/node/issues/4382/events","html_url":"https://github.com/nodejs/node/issues/4382","id":123362090,"number":4382,"title":"Enabling debug causes segfault","user":{"login":"domosapien","id":5354614,"avatar_url":"https://avatars.githubusercontent.com/u/5354614?v=3","gravatar_id":"","url":"https://api.github.com/users/domosapien","html_url":"https://github.com/domosapien","followers_url":"https://api.github.com/users/domosapien/followers","following_url":"https://api.github.com/users/domosapien/following{/other_user}","gists_url":"https://api.github.com/users/domosapien/gists{/gist_id}","starred_url":"https://api.github.com/users/domosapien/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/domosapien/subscriptions","organizations_url":"https://api.github.com/users/domosapien/orgs","repos_url":"https://api.github.com/users/domosapien/repos","events_url":"https://api.github.com/users/domosapien/events{/privacy}","received_events_url":"https://api.github.com/users/domosapien/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/node/labels/debugger","name":"debugger","color":"bfd4f2"},{"url":"https://api.github.com/repos/nodejs/node/labels/lts-watch-v4.x","name":"lts-watch-v4.x","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-12-21T21:26:24Z","updated_at":"2016-02-11T10:19:17Z","closed_at":null,"body":"Using the command line `node --debug=5859 file.js`, my application starts fine but then crashes with a segfault as soon as a request is received. If I remove the debug parameter, the segfault goes away. The same code works on v0.12.x and v4.2.x. Using version v5.3.0."},"comment":{"url":"https://api.github.com/repos/nodejs/node/issues/comments/182792764","html_url":"https://github.com/nodejs/node/issues/4382#issuecomment-182792764","issue_url":"https://api.github.com/repos/nodejs/node/issues/4382","id":182792764,"user":{"login":"javascriptui","id":9389136,"avatar_url":"https://avatars.githubusercontent.com/u/9389136?v=3","gravatar_id":"","url":"https://api.github.com/users/javascriptui","html_url":"https://github.com/javascriptui","followers_url":"https://api.github.com/users/javascriptui/followers","following_url":"https://api.github.com/users/javascriptui/following{/other_user}","gists_url":"https://api.github.com/users/javascriptui/gists{/gist_id}","starred_url":"https://api.github.com/users/javascriptui/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/javascriptui/subscriptions","organizations_url":"https://api.github.com/users/javascriptui/orgs","repos_url":"https://api.github.com/users/javascriptui/repos","events_url":"https://api.github.com/users/javascriptui/events{/privacy}","received_events_url":"https://api.github.com/users/javascriptui/received_events","type":"User","site_admin":false},"created_at":"2016-02-11T10:19:17Z","updated_at":"2016-02-11T10:19:17Z","body":"Looks like it didn't make the cut for the 4.3.0 release.\r\n\r\nAny news on when this might drop. This is pretty critical to back port as due to #3875 debugging with WebStorm is not really usable in 5.x can take 5 minutes due to a v8 issue regression that's awaiting to be fixed. And the 4.x release just segfault's due to this issue."}}