This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: backtrace() vs. _Unwind_Backtrace()
On Dec 5, 2003, at 3:28 PM, Andrew Pinski wrote:
On Dec 4, 2003, at 18:23, Bryce McKinlay wrote:
Hi David,
I have been working on a patch that revamps libgcj's stack tracing,
using the libgcc unwinder. I should be able to post it this weekend.
One outstanding issue is what to do about Windows, which apparantly
doesn't use the DWARF unwinder.
It is not just Windows, OpenBSD is the same way, but GCJ is not
support there because
the GC does not quite work with a.outb. In fact there are more
targets that do not
support DWARF unwinder than there are that do support it.
I'm not worried about every little platform, because stack traces (and
security) probably don't work there anyway. We can still run without
them. But on Windows, breaking stack traces would be a regression
because they do partially work there, although the current
implementation is pretty bogus when it comes to the calling-classloader
checks etc.
Regards
Bryce.