public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/12328] New: Ignore "const" for non-reference/pointer scalar
Date: Thu, 16 Dec 2010 17:34:00 -0000	[thread overview]
Message-ID: <bug-12328-4717@http.sourceware.org/bugzilla/> (raw)

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

           Summary: Ignore "const" for non-reference/pointer scalar
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned@sourceware.org
        ReportedBy: keiths@redhat.com


Source:

class myclass
{
 public:
  static void func(const int aa) {};
};

int
main (int argc, char *argv[])
{
  myclass::func (42);
}

Example:
(gdb) break myclass::func
the class myclass does not have any method named func
Hint: try 'myclass::func<TAB> or 'myclass::func<ESC-?>
(Note leading single quote.)
Make breakpoint pending on future shared library load? (y or [n]) n

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2010-12-16 17:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 17:34 keiths at redhat dot com [this message]
2010-12-16 17:37 ` [Bug c++/12328] Can't set breakpoint on method taking const, non-reference/pointer scalar parameter keiths at redhat dot com
2010-12-16 17:47 ` keiths at redhat dot com
2010-12-17 17:03 ` thahn01@t-online.de
2010-12-17 23:13 ` keiths at redhat dot com
2011-01-17  7:13 ` jan.kratochvil at redhat dot com
2011-02-06 18:17 ` jan.kratochvil at redhat dot com
2011-02-13  9:16 ` cvs-commit at gcc dot gnu.org
2011-02-13  9:24 ` jan.kratochvil 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=bug-12328-4717@http.sourceware.org/bugzilla/ \
    --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).