Re: Better tracebacks for C/C++ (and probably Ada & Fortran, too)

2010-02-01 Thread Florian Weimer
* Daniel Jacobowitz: > On Sun, Jul 26, 2009 at 12:42:46AM +0200, Florian Weimer wrote: >> I've built a small proof-of-concept library which creates Java-style >> tracebacks for C and C++ programs. In contrast to libc's backtrace() >> function, it uses DWARF debugging information when available, s

Re: Better tracebacks for C/C++ (and probably Ada & Fortran, too)

2009-10-16 Thread Michael Tautschnig
[...] (cool stuff) > > > > I'm now wondering whether something like this already exists (I > > couldn't find anything, though). I'm also not sure where to put this. > > gnatbind could be instructed (-E) to store non-symbolic traceback in > exception > occurrences, which would be printed out as

Re: Better tracebacks for C/C++ (and probably Ada & Fortran, too)

2009-07-29 Thread Daniel Jacobowitz
On Sun, Jul 26, 2009 at 12:42:46AM +0200, Florian Weimer wrote: > I've built a small proof-of-concept library which creates Java-style > tracebacks for C and C++ programs. In contrast to libc's backtrace() > function, it uses DWARF debugging information when available, so the > output is generally

Re: Better tracebacks for C/C++ (and probably Ada & Fortran, too)

2009-07-26 Thread George Danchev
Hi, > I've built a small proof-of-concept library which creates Java-style > tracebacks for C and C++ programs. In contrast to libc's backtrace() > function, it uses DWARF debugging information when available, so the > output is generally quite useful. Debugging information is extracted > from t

Better tracebacks for C/C++ (and probably Ada & Fortran, too)

2009-07-25 Thread Florian Weimer
I've built a small proof-of-concept library which creates Java-style tracebacks for C and C++ programs. In contrast to libc's backtrace() function, it uses DWARF debugging information when available, so the output is generally quite useful. Debugging information is extracted from the main executa