This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: where do stack traces get filled in?
- From: Tom Tromey <tromey at redhat dot com>
- To: Adam Megacz <gcj at lists dot megacz dot com>
- Cc: java at gcc dot gnu dot org
- Date: 12 Dec 2001 22:50:29 -0700
- Subject: Re: where do stack traces get filled in?
- References: <867krrllxh.fsf@megacz.com>
- Reply-to: tromey at redhat dot com
>>>>> "Adam" == Adam Megacz <gcj@lists.megacz.com> writes:
Adam> I see Throwable.stackTrace, but it never gets created in
Adam> Throwable.java or natThrowable.cc...
natThrowable.cc defines java::lang::Throwable::fillInStackTrace.
This does the actual work. It is deceptively short because it relies
on glibc functionality. (On ia64 we use _Jv_ia64_backtrace in
sysdep/ia64.c.)
Adam> BTW, that's really bizzarre how printStackTrace spawns a process to
Adam> run c++filt...
Andrew will have to address that. I forgot why we did it this way.
Maybe licensing?
Adam> Also, is SJLJ the only exception style that gcc supports on
Adam> win32?
As far as I know, that is indeed the case right now.
Tom