Stack trace, can we do something ?

Yazan Dabain yazan.dabain at gmail.com
Sat Mar 22 01:09:27 PDT 2014


On Saturday, 22 March 2014 at 05:52:49 UTC, deadalnix wrote:
> A paste is worth a long story : http://pastebin.com/XbL2dv9S
>
> That is really bad, and debugging horribly difficult. 
> Basically, no file/line numbers and no demangling.
>
> We tend to get used to it, unless it gets exceptionally bad, 
> but I'm pretty sure this kind of things can scare newcomers.

For ELF binaries with DWARF debug symbols, it's not that hard to
provide filenames and line numbers. I have some code which reads
the debug symbols without using any external libraries, but the
symbols produced by DMD are inaccurate which I would say would be
worse to display as inaccurate file/line info. Check
http://d.puremagic.com/issues/show_bug.cgi?id=10679. And so I
stopped at the proof of concept.
I have some time to resume work on that, I'll clean it up and
push it to github in hope that this issue is looked at.

In the meantime, you can use addr2line to get file/line
information and I provide a way to do that automatically with
this library: https://github.com/yazd/backtrace-d


More information about the Digitalmars-d mailing list