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.

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

src: fix build error with lldb 3.8 #109

Merged
merged 1 commit into from
Jun 30, 2017
Merged

src: fix build error with lldb 3.8 #109

merged 1 commit into from
Jun 30, 2017

Conversation

bnoordhuis
Copy link
Member

Missed llscan.cc, cc @hhellyer.

bnoordhuis referenced this pull request Jun 29, 2017
* src: use explicit imports
Replace `using namespace lldb` with explicit `using lldb::<name>`
imports.

* test: fix scan-test.js with node >= 8.1.0
The object change that commit b73e042 ("src,test: support node.js >= 8")
from April addressed has been reverted again in 8.1.0.  Update the test.
Refs: nodejs/node#13374

* src: print builtins and unnamed stack frames
Previously, `v8 bt` would exclude frames that didn't map to a C++ symbol
or a JS stack frame.  llnode does not currently know how to identify the
stack frames of V8 builtins so those were omitted as well.

This commit makes those stack frames visible and introduces a heuristic
(in lldb >= 3.9) where frames whose PC is inside a WX memory segment are
assumed to belong to V8 builtins.

Fixes: #99
* fixup! SBMemoryRegionInfo is lldb >= 3.9

Fix: #99
PR-URL: #104
Reviewed-By: Fedor Indutny <fedor@indutny.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
indutny

This comment was marked as off-topic.

cjihrig

This comment was marked as off-topic.

@hhellyer
Copy link
Contributor

Merging, since it's approved and fixes a build error.

@hhellyer hhellyer merged commit 5ab458c into nodejs:master Jun 30, 2017
@bnoordhuis
Copy link
Member Author

@hhellyer I took the liberty to force-push your merge away. As a rule of thumb, we only rebase on top, not merge. New commit: 5d63284

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants