This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFC: stack trace generation


Andrew Haley wrote:

> What I was more interested in was changing the file/line lookup
> code in NameFinder, and whether or not a shared library DWARF-2
> parser would be a part of that. I've improved what I posted earlier
> a great deal, so it is not unreasonably slow, and produces fairly
> accurate debug traces.

My first reaction to this is that I'm a bit reluctant to put DWARF2
parsing into libgcj, but if that's agreed by common consent to be a
good solution I won't argue.


However, if we can fix this PLT problem with a change to gcc I believe
that the reflection metadata was is the right way to go. To a large
extend the DWARF debug info and the reflection metadata are redundant,
but we support metadata on every target and DWARF info on only some of
them.


Class metadata will be used to implement the IP->method/class mapping. Dwarf2 will be used to implement Throwable.printStackTrace(), ie the IP->source file/line number mapping. This replaces the call to addr2line which is quite inefficient and adds a dependency on an external tool. So, I think the Dwarf2 solution is the way to go.

Regards

Bryce


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]