public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/11734] New: break c::bar() broken, can't find bar
Date: Mon, 21 Jun 2010 06:59:00 -0000	[thread overview]
Message-ID: <20100621065928.11734.dje@google.com> (raw)

With the appended testcase, I get the following:

$ g++ --version
g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
[...]
$ g++ -g foo.cc foo2.cc
$ ./gdb -nx ./a.out
GNU gdb (GDB) 7.1.50.20100619-cvs
[...]
(gdb) start
[...]
(gdb) b 'c::foo()'
the class c does not have any method named foo()
Hint: try 'c::foo()<TAB> or 'c::foo()<ESC-?>
(Note leading single quote.)
Make breakpoint pending on future shared library load? (y or [n])

This is a regression from 7.1.

fyi, the following does work:

(gdb) b c::foo     # Do this first ...
(gdb) b c::foo()   # ... and then this works.

---
foo.h:

class c
{
 public:
  void foo ();
};
---
foo.cc:

#include "foo.h"

int
main ()
{
  c* p = new c;
  p->foo ();
  return 0;
}
---
foo2.cc:

#include "foo.h"

void
c::foo ()
{
}

-- 
           Summary: break c::bar() broken, can't find bar
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: dje at google dot com
                CC: gdb-prs at sourceware dot org
 GCC build triplet: amd64-linux
  GCC host triplet: amd64-linux
GCC target triplet: amd64-linux


http://sourceware.org/bugzilla/show_bug.cgi?id=11734

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2010-06-21  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21  6:59 dje at google dot com [this message]
2010-06-21 20:38 ` [Bug c++/11734] " keiths at redhat dot com
2010-06-21 21:01 ` keiths at redhat dot com
2010-06-22  1:23 ` keiths at redhat dot com

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=20100621065928.11734.dje@google.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).