Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: viju vincent <vijuvince@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Issue with printing binary operator overloaded function on GDB 7.2
Date: Mon, 27 Dec 2010 19:38:00 -0000	[thread overview]
Message-ID: <4D18EB0D.5080200@redhat.com> (raw)
In-Reply-To: <AANLkTinkkBPcJA5cSAe_oWctit1cJD5Ad3GhpZKnpzn=@mail.gmail.com>

On 12/22/2010 11:53 PM, viju vincent wrote:

>   * From GDB log
> {{{
>     print base::operator!=
> $17 = {bool (const base * const, const void&)} 0x9784
> <base::operator!=(void const&) const>
> (gdb) FAIL: gdb.cp/cpexprs.exp: print base::operator!=
> }}}

What's a "const void&"? :-)

FWIW, I've tried CVS head with the following GCCs: 4.4.5 20101112 (Red 
Hat 4.4.5-2), 4.6.0 20101227 (experimental), and 4.5.2 (GCC), and none 
of them exhibit the problem (cpexprs.exp passes as I expect it to).

What does the debug info say the type of base::operator!= is? I suspect 
it is wrong. [You can use "readelf -wi" or "eu-readelf -wi" to inspect 
the debug info.]

Keith


  reply	other threads:[~2010-12-27 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  7:53 viju vincent
2010-12-27 19:38 ` Keith Seitz [this message]
2010-12-27 19:44   ` Andreas Schwab
2010-12-27 20:05     ` Keith Seitz

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=4D18EB0D.5080200@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=vijuvince@gmail.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