This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC: stack trace info for interpreter frames

From: Tom Tromey <tromey at redhat dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: Java Patch List <java-patches at gcc dot gnu dot org>
Date: 29 Aug 2002 10:24:49 -0600
Subject: Re: RFC: stack trace info for interpreter frames
References: <87lm6qburq.fsf@fleche.redhat.com><15726.2988.825397.14862@cuddles.cambridge.redhat.com>
Reply-to: tromey at redhat dot com

>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:

Andrew> The double-length array is kinda kludgey.

I agree.  I added a structure that is filled in instead.  This cleaned
things up nicely.

Andrew> It would be nice to have a small comment explaining the
Andrew> constructor/destructor trick.  "Indicate that we're the top-most
Andrew> interpreter frame." doesn't quite explain it all.

Good idea, done.  I also added a comment at the start/end functions
explaining what they're there for.

I'll check this in a bit later.  I may change it to demangle the
method signature first.

Tom

Follow-Ups:
- Re: RFC: stack trace info for interpreter frames
  - From: Tom Tromey

References:
- RFC: stack trace info for interpreter frames
  - From: Tom Tromey
- RFC: stack trace info for interpreter frames
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]