backtrace() vs. _Unwind_Backtrace()

David Mosberger davidm@napali.hpl.hp.com
Fri Dec 5 01:34:00 GMT 2003

• Previous message (by thread): [PATCH] [MinGW] for Review: Add UNICODE support to MinGW libgcj (UPDATED)
• Next message (by thread): backtrace() vs. _Unwind_Backtrace()
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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.
	--david

---

• Previous message (by thread): [PATCH] [MinGW] for Review: Add UNICODE support to MinGW libgcj (UPDATED)
• Next message (by thread): backtrace() vs. _Unwind_Backtrace()
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Java mailing list