walking the stack

Tue Apr 16 03:42:00 GMT 2002

Bryce McKinlay <bryce@waitaki.otago.ac.nz> 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. It would also be good to have some
> way to recognise interpreter/JIT frames and call into them for their
> own stack info.

Given that with exception reporting you're only talking about
package/class/method/line numbers couldn't these bits be extracted
when compiling .java or .class and stored somewhere for this purpose?
With the .so, .dll, or executable seems elegant and maybe this is what
DWARF2 is. 
Brian
-- 
Brian Jones <cbj@gnu.org>