From: Daniel Jacobowitz <drow@false.org>
To: Andrew Haley <aph@redhat.com>
Cc: Jeff Johnston <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Java Inferior Call Take 2
Date: Mon, 02 Aug 2004 20:20:00 -0000 [thread overview]
Message-ID: <20040802201909.GA1618@nevyn.them.org> (raw)
In-Reply-To: <16654.23217.847150.837143@cuddles.cambridge.redhat.com>
On Mon, Aug 02, 2004 at 04:16:01PM +0100, Andrew Haley wrote:
> Andrew Haley writes:
> > Daniel Jacobowitz writes:
> > > On Mon, Jul 26, 2004 at 03:49:30PM -0400, Jeff Johnston wrote:
> > > > Ping.
> > >
> > > I was waiting for Andrew to try fixing up gcj so that we could avoid
> > > the method name problem. Andrew, are you going to have time to do
> > > that, or should we pursue the hack for now after all? I'd much rather
> > > it be fixed.
> >
> > Sorry Daniel, I've been away. You are right: it should be fixed in
> > gcc. I will do this as soon as I get stuff sorted out.
>
> Okay, I've made a patch but I'm not sure it's what you want.
>
> This is a snippet from a typical file:
>
> .long 0x9ca | .long 0x851
> .byte 0x1 .byte 0x1
> .string "java.lang.Class.forName(java.lang.String)" | .string "forName"
> .byte 0x3 .byte 0x3
>
> Is that what you want? I've only made the change for method names;
> field names are as before.
That's what I had in mind. What do field names look like? I thought
they were already in the shortened form.
If you want to send me the patch to try, I'll put it together with the
Java inferior call support and see if everything lines up right.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-08-02 20:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 20:53 Jeff Johnston
2004-06-11 17:49 ` Jeff Johnston
2004-06-17 3:06 ` Daniel Jacobowitz
2004-06-17 20:52 ` Jeff Johnston
2004-06-19 23:59 ` Daniel Jacobowitz
2004-06-21 10:49 ` Andrew Haley
2004-06-21 15:17 ` Andrew Haley
2004-06-23 11:06 ` Andrew Haley
2004-06-23 13:47 ` Daniel Jacobowitz
2004-06-23 16:06 ` Andrew Haley
2004-06-23 16:08 ` Daniel Jacobowitz
2004-06-23 21:55 ` Jeff Johnston
2004-06-23 23:01 ` Daniel Jacobowitz
2004-06-24 17:57 ` Tom Tromey
2004-07-06 21:47 ` Jeff Johnston
2004-07-26 19:49 ` Jeff Johnston
2004-07-26 19:51 ` Daniel Jacobowitz
2004-08-02 10:17 ` Andrew Haley
2004-08-02 15:17 ` Andrew Haley
2004-08-02 20:20 ` Daniel Jacobowitz [this message]
2004-08-03 18:45 ` Andrew Haley
2004-08-16 13:08 ` Andrew Haley
2004-08-16 13:18 ` Daniel Jacobowitz
2004-08-16 20:32 ` Daniel Jacobowitz
2004-08-16 20:35 ` Daniel Jacobowitz
2004-08-24 18:53 ` [RFA]: Java Inferior Call Take 3 Jeff Johnston
2004-08-24 19:05 ` Michael Chastain
2004-08-24 19:28 ` Jeff Johnston
2004-08-24 19:10 ` Michael Chastain
2004-08-24 19:48 ` Andrew Cagney
2004-09-01 4:51 ` Jim Blandy
2004-09-09 23:41 ` Jeff Johnston
2004-09-10 20:12 ` Jim Blandy
2004-09-15 22:58 ` Jeff Johnston
2004-09-20 18:23 ` Jim Blandy
2004-09-20 20:19 ` Jeff Johnston
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=20040802201909.GA1618@nevyn.them.org \
--to=drow@false.org \
--cc=aph@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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