Idea for stack traces

Sat Mar 9 02:48:00 GMT 2002

Bryce McKinlay writes:
 > Andrew Haley wrote:
 > 
 > >Offhand, my first reaction to this is that we'd be duplicating the
 > >DWARF info for no particular good effect. Writing a tiny DWARF
 > >interpreter that can only access symbols and addresses which lives in
 > >libgcj would not be so very hard, and we could arrange for this info
 > >to be emitted even on targets that don't use DWARF by default.
 > >
 > 
 > The advantage of the scheme I described is that it doesn't require any 
 > DWARF info - only the reflective data which is available in every GCJ 
 > class even if there is no debugging info.
Yes, that is a very good point, I admit. I kinda hate the redundancy
in what we're doing, the way mych of the reflected info is duplicated
in the debug data. Oh well.
Andrew.