-
Notifications
You must be signed in to change notification settings - Fork 257
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
Add the Frame::sp
method to get the frame's stack pointer
#341
Conversation
1b8c048
to
bdd2f33
Compare
No idea what is up with the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor nits about the test, but otherwise seems good to me!
|
||
let mut is_recursive_stack_references = false; | ||
backtrace::resolve(frame.ip(), |sym| { | ||
is_recursive_stack_references |= (LIBBACKTRACE || GIMLI_SYMBOLIZE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the LIBBACKTRACE || GIMLI_SYMBOLIZE
part here necessary? It looks like this handles a non-present name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we can't rely on symbolication, then we can't determine which stack frames are the ones we are interested in (due to inlining happening or not), and therefore don't know when to pop from our stack of on-stack references.
Hm ok so the failing test here seems semi-legitimate. It looks like the test is panicking but in emulation the panic fails for... whatever reason. The test harness is capturing output to print later but the abort means it doesn't get printed. Anyway passing
|
Okay! I've got |
👍 |
r? @alexcrichton