From: Elena Zannoni <ezannoni@redhat.com>
To: tromey@redhat.com
Cc: David Carlton <carlton@math.stanford.edu>,
gdb-patches@sources.redhat.com
Subject: Re: [rfa] allocate_objfile(NULL, 0)
Date: Tue, 04 Feb 2003 18:02:00 -0000 [thread overview]
Message-ID: <15936.296.432592.13041@localhost.redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2003-02-04 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 23:41 David Carlton
2003-01-11 0:00 ` Elena Zannoni
2003-01-11 0:12 ` David Carlton
2003-01-17 23:32 ` Tom Tromey
2003-02-04 18:02 ` Elena Zannoni [this message]
2003-02-04 18:07 ` Tom Tromey
2003-02-04 18:04 ` Elena Zannoni
2003-02-04 22:21 ` David Carlton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15936.296.432592.13041@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox