This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa] allocate_objfile(NULL, 0)
- From: Elena Zannoni <ezannoni at redhat dot com>
- To: tromey at redhat dot com
- Cc: David Carlton <carlton at math dot stanford dot edu>, gdb-patches at sources dot redhat dot com
- Date: Tue, 4 Feb 2003 13:06:32 -0500
- Subject: Re: [rfa] allocate_objfile(NULL, 0)
- References: <ro1hecgd149.fsf@jackfruit.Stanford.EDU><15903.24492.446475.747803@localhost.redhat.com><ro1y95sbl4c.fsf@jackfruit.Stanford.EDU><87d6mv4aft.fsf@fleche.redhat.com>
Tom Tromey writes:
> >>>>> "David" == David Carlton <carlton@math.stanford.edu> writes:
>
> David> I'm no Java expert, but here's the situation as I understand
> David> it. When evaluating Java code, sometimes you have to generate
> David> new Java classes in an unpredictable manner.
>
> David> Alas, I don't know enough Java to be able to create a test
> David> case.
>
> I don't know very much about this part of gdb. However, I can say
> that in libgcj we create classes on the fly to represent arrays. Even
> the simplest Java program will create at least one such array (for
> String[]):
>
> public class t
> {
> public static void main(String[] args)
> {
> System.out.println(args.length);
> }
> }
>
> Then compile with:
>
> gcj --main=t -o t t.java
>
>
> There is at least one longstanding gdb SEGV that happens when trying
> to re-run a Java executable. This happens in most, but not every, gdb
> session.
>
> Unfortunately I can't try your patch in the near future.
>
> Tom
David, Tom, could a little gdb test be created and put in gdb.java?
elena