-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Wrong debug info #7471
Comments
still present? how to reproduce? |
Can you check in gdb/lldb (add a breakpoint before the raise and then print the backtrack when execution stops) and report whether the line number is correct or zero? First case means there is a bug in the dwarf decoder, zero means there is a bug in the debug information passed to llvm ir. |
Is there a reproducible example? |
I've reproduced it with kemal, perhaps there are other prerequisites. |
It's quite easy to reproduce. I spot it from time to time but never gathered the courage to analyze it. |
It might have sth to do with |
I just ran into this (linux, OS X is OK) see top line of this backtrace: |
OK I was asked to add some other "classes" of wrong debug info to this issue, so I guess it'll be a grab bag of sorts... Here's one: Here's how to repro. Linux ubuntu. From a crystal git repo:
Use it somehow:
Same trace, in gdb
Appears crystal is identifying some lines as part of the crystal std lib crystal files (heapify et al lines) that are actually part of a 3rd party library. Or maybe this example is unrelated since it doesn't have the 255's? hmm |
Also somewhat related: #8352 |
Possibly related? the question marks in the backtrace here: #8584 |
#9209 may have some clues. Does anybody have a way to repro this easily these days? |
I'm hoping this was fixed in 2d02e52 |
Sometimes I'm seeing stacktraces with frames having wrong line (and possible column) numbers.
It seems to me there's some overflow going on (
0
/255
values).Example stacktrace - notice column numbers with
0
and255
:Tested with Crystal
0.27.2
and macOS10.13.6
.The text was updated successfully, but these errors were encountered: