RFC: stack trace generation

Mon Jul 19 19:37:00 GMT 2004

Andrew Haley wrote:
>> Sounds reasonable. We can't insist that in order for libgcj stack
> traces to work we must use a specific debug info format. However, if
> all we lose on non-DWARF 2 platforms is line numbers/ source files I
> can't see any big objection.
>> One thing I should point out for lurkers: we're using DWARF 2 to mean
> two different things here: DWARF 2 unwinder data and DWARF 2 debug
> info. If we can do everything except printStackTrace() with the
> former, that's unlikely to cause problems.
>> One other thing: as long as we stick to the unwinder library in libgcc
> we'll be able to cope with platforms like ARM and IA-64, which have
> their own ideas about unwinder info.

This would also allow dropping "-fno-omit-frame-pointer",
which can make a difference on register starved architectures...
Ranjit.
-- 
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/