This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: backtrace() vs. _Unwind_Backtrace()
- From: "david daney" <ddaney at avtrex dot com>
- To: "Bryce McKinlay" <bryce at mckinlay dot net dot nz>,<davidm at hpl dot hp dot com>
- Cc: <java at gcc dot gnu dot org>
- Date: Thu, 4 Dec 2003 21:52:08 -0800
- Subject: RE: backtrace() vs. _Unwind_Backtrace()
On Dec 5, 2003, at 2:34 PM, David Mosberger wrote:
>> While debugging another problem, I noticed that libjava currently
>> attempts to use libc's backtrace() function to create a stack trace
>> (libjava/gnu/gcj/runtime/natStackTrace.cc). Recently, libgcc got an
>> _Unwind_Backtrace() function, which I think should do exactly what's
>> needed there (in combination with _Unwind_GetIP()), so I think it
>> would make sense to switch to _Unwind_Backtrace() instead.
>
>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.
How does your patch compare to sysdep/dwarf2-backtrace.cc ?
I have some improvements to it that I was thinking about posting.
David Daney