This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Stack traces, etc.
- From: Tom Tromey <tromey at redhat dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: Mark Wielaard <mark at klomp dot org>, java at gcc dot gnu dot org
- Date: 03 Dec 2002 03:09:22 -0700
- Subject: Re: Stack traces, etc.
- References: <15847.65022.630354.996182@cuddles.cambridge.redhat.com><1038651258.12096.128.camel@elsschot><15848.39333.183099.838746@cuddles.cambridge.redhat.com><1038758828.12098.189.camel@elsschot><15851.49705.819280.310973@cuddles.cambridge.redhat.com>
- Reply-to: tromey at redhat dot com
>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:
Andrew> Revised, VMThrowable reinstated, testing now. Checkin
Andrew> tomorrow unless anyone complains.
No complaint here.
Andrew> + #ifdef INTERPRETER
Andrew> + extern void _Jv_StartOfInterpreter (void);
Andrew> + extern void _Jv_EndOfInterpreter (void);
Anthony, you once said your stack trace patch used the address of the
libffi stub to keep track of interpreted frames. Can you tell me how
to do this? How do I find the size of the stub?
This seems like a cleaner implementation, provided we get the GC
behavior correct. And it will fix PR 8170 (we need a hack similar to
the above for JNI methods).
Tom