This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: RFC: stack trace info for interpreter frames
- From: Andrew Haley <aph at cambridge dot redhat dot com>
- To: Anthony Green <green at redhat dot com>
- Cc: Tom Tromey <tromey at redhat dot com>,Java Patch List <java-patches at gcc dot gnu dot org>
- Date: Thu, 5 Sep 2002 14:17:54 +0100 (BST)
- Subject: Re: RFC: stack trace info for interpreter frames
- References: <87lm6qburq.fsf@fleche.redhat.com><1030751996.2445.11.camel@dhcppc2>
Anthony Green writes:
> On Wed, 2002-08-28 at 13:20, Tom Tromey wrote:
> > * Is the technique of putting dummy functions before and after the
> > interpreter function portable enough? It works ok for me on my
> > Linux box, but that's hardly definitive. (If not this approach,
> > then what?)
>
> I don't think we should count on this when people may compile with
> -ffunction-sections, giving the linker an easy opportunity to reorder
> functions.
The way to fix this is to put all the interpreter code in its own
section, with markers at the top and bottom.
> The approach I've take in my security model experiments is to register a
> PC region when the method's closure is created. I'll try to finish my
> patches this week.
Well, that's an interesting approach.
Andrew.