{{ message }}
src: use new SystemPointerSize constant#300
Closed
mmarchini wants to merge 1 commit into
Closed
Conversation
This alone should fix a lot of issues. It was enough to get a reasonable stack trace from a Node.js v12.3.0 core dump, ran with --interpreted-frames-native-stack. For some reason `v8 bt` is not working when running Node.js in lldb.
cjihrig
approved these changes
Sep 27, 2019
mmarchini
added a commit
that referenced
this pull request
Sep 27, 2019
This alone should fix a lot of issues. It was enough to get a reasonable stack trace from a Node.js v12.3.0 core dump, ran with --interpreted-frames-native-stack. For some reason `v8 bt` is not working when running Node.js in lldb. PR-URL: #300 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This alone should fix a lot of issues. It was enough to get a reasonable
stack trace from a Node.js v12.3.0 core dump, ran with
--interpreted-frames-native-stack. For some reason
v8 btis notworking when running Node.js in lldb.