Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: tromey@redhat.com
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: java inferior function call support
Date: Wed, 24 Mar 2004 21:33:00 -0000	[thread overview]
Message-ID: <vt21xnivske.fsf@zenia.home> (raw)
In-Reply-To: <87y8pqxa9q.fsf@fleche.redhat.com>

Tom Tromey <tromey@redhat.com> writes:

> >>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
> 
> Daniel> I'm not at all sure about the vtable changes.  They should be
> Daniel> compatible, because gcj does try to follow the C++ ABI.  If you'll send
> Daniel> a testcase, I'll take another look and see what I'm missing.
> 
> Yeah, a gcj vtable looks pretty much like the vtable of a C++ class
> with only a single superclass.  It is a bit odd in that there are a
> couple of vtable slots that don't actually point to methods, but I
> think this shouldn't matter to gdb.
> 
> If gdb uses C++ RTTI, then that would be a problem, since gcj doesn't
> generate the same sort of RTTI information.

I don't think it does.  When GDB wants to find an object's run-time
type, it finds the address of its vtable, looks up the minimal symbol
whose value is that address, demangles that, and extracts the class's
name from the demangled vtable name.  Then it uses debugging info from
there.

But I don't think there's much in GDB that looks at the RTTI itself.


  reply	other threads:[~2004-03-24 21:33 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 [this message]
     [not found]   ` <4060B653.2050400@redhat.com>
2004-03-25  0:18     ` Daniel Jacobowitz
2004-03-23 19:21 ` David Carlton
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=vt21xnivske.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=drow@false.org \
    --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