This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
libunwind & _Unwind_Backtrace
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: java at gcc dot gnu dot org
- Date: Tue, 17 May 2005 15:30:35 -0700 (PDT)
- Subject: libunwind & _Unwind_Backtrace
- Reply-to: sje at cup dot hp dot com
I was looking at building java on IA64 HP-UX and I found that the java
library calls _Unwind_Backtrace(). Now the unwind interface for C++ is
standardized and does not include this routine, apparently this was
added for java but isn't part of any standard.
The reason this affects me is that on IA64 HP-UX we are currently using
the system libunwind and it does not include this routine. So, to build
java on IA64 HP-UX I have to provide this somehow. I am looking at
several options and would like some opinions.
Convert g++ (and java) to use the GCC libunwind. I don't really like
this idea because I think that it is confusing to have two libunwinds
and it could hinder the compatibility objects compiled with GCC and
objects compiled with the system compilers.
Create my own _Unwind_Backtrace routine separate from libunwind. This
should be possible using the existing system interface to libunwind,
but where would it live then? Could I put it in the java runtime
library?
Find a way to avoid using _Unwind_Backtrace. I don't know if this
is possible or not.
Thoughts?
Steve Ellcey
sje@cup.hp.com