From: David Carlton <carlton@kealia.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: java inferior function call support
Date: Tue, 23 Mar 2004 19:21:00 -0000 [thread overview]
Message-ID: <yf2smfzpdx3.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <40608A03.1070808@redhat.com> (Jeff Johnston's message of "Tue, 23 Mar 2004 14:03:31 -0500")
On Tue, 23 Mar 2004 14:03:31 -0500, Jeff Johnston <jjohnstn@redhat.com> said:
> There a few differences between Java and C++ that require handling.
> First of all, the Java debug info for a member has a fully qualified
> name including prototype. There is an open bugzilla bug against gcj
> for this, however, I think some rethinking may be required.
I'm not thrilled with fixing this in GDB instead of in GCJ. Including
the fully qualified name means that, to get just the member name, we
have to do some parsing, which we'd like to get away from. Treating
Java differently from C++ increases the number of special cases in
GDB; given the almost completely unmaintained state of the Java code
in GDB, that makes me very nervous. (I don't supposed you're
interesting in being a GDB Java maintainer?) Also, at least as far as
the GCC Bugzilla report says, GCJ's debug info isn't consistent -
sometimes it gives the fully qualified name, sometimes it just gives
some sort of weird name which doesn't make sense at all.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-03-23 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 19:03 Jeff Johnston
2004-03-23 19:10 ` Daniel Jacobowitz
2004-03-24 20:38 ` Tom Tromey
2004-03-24 21:33 ` Jim Blandy
[not found] ` <4060B653.2050400@redhat.com>
2004-03-25 0:18 ` Daniel Jacobowitz
2004-03-23 19:21 ` David Carlton [this message]
2004-03-23 22:35 ` Jeff Johnston
2004-03-23 22:48 ` 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=yf2smfzpdx3.fsf@hawaii.kealia.com \
--to=carlton@kealia.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