-
Notifications
You must be signed in to change notification settings - Fork 253
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
Inline Frame Regression on Linux in 0.3.17 #186
Comments
FWIW, I can't get inline frames to show up on macOS at all; but that's probably unrelated. |
alexcrichton
added a commit
that referenced
this issue
May 16, 2019
This commit fixes an accidental regression with #185 where libbacktrace was updated to match the standard library by always returning the symbol table symbol. Turns out though this library was one-upping the standard library by consulting debuginfo (what it was previously doing) because debuginfo can have more accurate symbol information for inline functions, for example. The fix here is to always prefer the debuginfo function name, if present, and otherwise fall back to the symbol table symbol if necessary. Closes #186
Oops, sorry for the regression! Thanks for the quick catch though and the report! I think this should be fixed at #187 |
That was fast :) Thanks for the quick turnaround! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 0.3.17 function names for inline frames are now incorrectly showing the name of the symbol they are inlined into. Repro case added below.
I haven't looked at the details, but it might have to do with #185. It is correct that the symbol table often contains better names than DWARF debug info for regular symbols, but this is obviously not the case for inline symbols.
Repro Code
Expected Backtrace: (truncated)
Actual Backtrace: (truncated)
The text was updated successfully, but these errors were encountered: