public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joost van der Sluis <joost@cnoc.nl>
Cc: gdb@sourceware.org
Subject: Re: Handling of c++ function members
Date: Mon, 26 Sep 2011 20:38:00 -0000	[thread overview]
Message-ID: <CAN9gPaE0K+z-8H5NyHmHg2KcYz2QEAHOy=eXC28bva0-zD4xhg@mail.gmail.com> (raw)
In-Reply-To: <1317055596.23338.12.camel@feddie.cnoc.lan>

On Mon, Sep 26, 2011 at 12:46 PM, Joost van der Sluis <joost@cnoc.nl> wrote:
> Hi all,
>
> I've been looking at the code which handles calling c++ function members
> and the Dwarf specifications. Is came to the conclusion that gcc does
> not generate valid Dwarf-debuginfo for those function members, but a
> work-around which is also implemented in gdb, namely in gnu-v2-abi.c.
>
> Is my conclusion right?

Can you be a little more specific, maybe an example?

There are definitely oddities in the GCC debug info, but the
workarounds I remember are in the DWARF reader.

-- 
Thanks,
Daniel

  reply	other threads:[~2011-09-26 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 16:46 Joost van der Sluis
2011-09-26 20:38 ` Daniel Jacobowitz [this message]
2011-09-26 21:01   ` Joost van der Sluis
2011-09-27 15:05     ` Joost van der Sluis
2011-09-27 16:01       ` Joost van der Sluis
2011-09-30 14:42       ` Daniel Jacobowitz
2011-09-30 15:53         ` Joost van der Sluis
2011-09-30 18:50           ` Jan Kratochvil
2011-09-30 20:37             ` Joost van der Sluis
2011-10-02 13:51         ` Joost van der Sluis
2011-10-05 18:56           ` Tom Tromey

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='CAN9gPaE0K+z-8H5NyHmHg2KcYz2QEAHOy=eXC28bva0-zD4xhg@mail.gmail.com' \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=joost@cnoc.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).