From: Keith Seitz <keiths@redhat.com>
To: tromey@redhat.com
Cc: gdb@sourceware.org
Subject: Re: Some java questions
Date: Tue, 09 Sep 2008 23:36:00 -0000 [thread overview]
Message-ID: <48C70822.3070905@redhat.com> (raw)
In-Reply-To: <m3bpyx9fy7.fsf@fleche.redhat.com>
Tom Tromey wrote:
> To support Java 1.5, we had to add return types to name mangling.
> These are needed due to covariant return types.
Ah, okay, that explains a lot.
> What you are seeing here is just how the demangler chooses to print
> this information. E.g., when I 'nm --demangle=java' a simple java
> program, I see:
>
> 0804891e T h.main(java.lang.String[])void
> U java.lang.Object.toString()java.lang.String
> [etc]
Yuck. Nonetheless, it looks like that's the status quo, and I need to
fix it. I'll also look into either fixing the "info func" printout or at
least add a test case for that so that it doesn't disappear.
Keith
prev parent reply other threads:[~2008-09-09 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 19:44 Keith Seitz
2008-09-09 21:18 ` Tom Tromey
2008-09-09 21:31 ` Daniel Jacobowitz
2008-09-09 23:39 ` Keith Seitz
2008-09-09 23:36 ` Keith Seitz [this message]
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=48C70822.3070905@redhat.com \
--to=keiths@redhat.com \
--cc=gdb@sourceware.org \
--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