This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: walking the stack
Bryce McKinlay writes:
> Adam Megacz wrote:
>
> >Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:
> >
> >>>Is there any way to get line numbers this way, or would the stack
> >>>trace be limited to class/method names?
> >>>
> >>No, there would be no way to get line number info from a stripped binary
> >>- it would just be class/method names.
> >>
> >
> >So would it make sense to have a three stage fallback here
> >(DWARF2->addr2line()->reflection_data)?
> >
>
> Yeah - although ideally we'd be able to get rid of addr2line
> alltogether if we can do dwarf2.
In the context of stack unwinding, DWARF 2 refers to the unwind data
that the runtime uses, not information used by a debugger. Modulo
IA-64, our unwinder runtime uses DWARF 2 unwind info regardless of
whatever format is used for debug info. Therefore, something that can
read debug info to get line numbers will still be needed.
> It would also be good to have some way to recognise interpreter/JIT
> frames and call into them for their own stack info.
Oh yes.
Andrew.