Fix Issue 18068 - No file names and line numbers in stack trace - Again#2278
Fix Issue 18068 - No file names and line numbers in stack trace - Again#2278wilzbach merged 1 commit intodlang:stablefrom JinShil:fix_18068_again
Conversation
|
Thanks for your pull request, @JinShil! Bugzilla references
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub fetch digger
dub run digger -- build "stable + druntime#2278" |
|
How many times do we need to fix this and how can we prevent it from breaking? |
|
Well, our CIs don't suffer from the problem for some reason. |
Is it dependent on the distro? |
|
Yeah, we're probably not on a rolling distro in CI: #2230 (comment) This update on Arch broke it: |
|
Hmm I use Arch too (with glibc @nemanja-boric-sociomantic @Boris-Barboris what do you to run into this issue? void main()
{
throw new Exception("aa");
}works fine for me. |
|
I'll use lxc arch container for demonstration (but i noticed the bug on my main non-containerized arch install):
P.S. I can provide ssh access to the container if you need. |
|
Same here, with nightly: |
|
Okay I looked a bit more into this and the GNU's binutils linker (aka DetailsDebug sectionsOn my machine: In Docker: With this PR on Docker: Code sectionsIn fact when looking at it in gdb, the first header that gets iterated when linked with |
wilzbach
left a comment
There was a problem hiding this comment.
Makes sense to me now. I rebased to stable, s.t. we can get it in for 2.082.
In terms of reproducing this the best option would probably be to add a machine with a new glibc + kernel to the Buildkite tester ...
No description provided.