public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "drow at sources dot redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/11289] New: Can not set FILE:CLASS::FUNCTION breakpoints
Date: Tue, 16 Feb 2010 20:12:00 -0000	[thread overview]
Message-ID: <20100216201257.11289.drow@sources.redhat.com> (raw)

I have a patch which adds these two tests to overload.exp:

gdb_test "list ${srcfile}:foo::overloadfnarg(int)" "int foo::overloadfnarg"
gdb_test "list ${srcfile}:'foo::overloadfnarg(int)'" "int foo::overloadfnarg"

They both fail (before and after the patch).  locate_first_half has a comment
suggesting it should find "overload.cc:" in this case, but instead it finds
"overload.cc:foo::".  So we decide that must be a class, and never look for a
file named overload.cc.

-- 
           Summary: Can not set FILE:CLASS::FUNCTION breakpoints
           Product: gdb
           Version: 7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: drow at sources dot redhat dot com
                CC: gdb-prs at sourceware dot org


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

------- 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-02-16 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 20:12 drow at sources dot redhat dot com [this message]
2010-02-16 20:52 ` [Bug c++/11289] " cvs-commit at gcc dot gnu dot org
2010-02-16 22:38 ` tromey 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=20100216201257.11289.drow@sources.redhat.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).