-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
gdb has the wrong source location with many macros #18285
Labels
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
C-bug
Category: This is a bug.
Comments
alexcrichton
added
the
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
label
Oct 24, 2014
Might be related to #23480. |
This bug makes debugging errors returned through |
huonw
added
the
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
label
Jan 5, 2016
Will this magically get fixed when #23480 is fixed? |
Yeah, this looks like a consequence of #23480 / #39450. |
This seems to be fixed, at least from my test running the same source with rustc 1.37 Source locations are valid for both call sites.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
C-bug
Category: This is a bug.
The line number for the stack frame of
main::foo
says it's on line 4, when it should actually be lower than that. I have noticed, however, that if there's only one macro (e.g. call2 goes away) the source location is correct. This may be a bug in debuginfo, but it may also be a bug in macros in general (source locations aren't always quite correct I think).cc @michaelwoerister
The text was updated successfully, but these errors were encountered: