public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/12803] Regression: const/volatile method functions linespec `break'
Date: Tue, 24 May 2011 16:52:00 -0000 [thread overview]
Message-ID: <bug-12803-4717-XQtT9SKB1O@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12803-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12803
--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2011-05-24 16:51:46 UTC ---
(In reply to comment #1)
> "break 'C::m() const'" does work, but you must "set lang c++" first.
Aha, again, OK.
> This is because keep_name_info in linespec.c is only called when the current
> language is set to c++. We could change this to unconditionally call this;
> from decode_compound, it should be relatively safe (assertion untested). What
> do you think?
Yes, I would prefer it, it was already so in pre-phys and getting current
language correctly set does not always work.
> The volatile case is a bug: keep_name_info does not include it. When it is
> added, then it works. I can prepare a patch and some tests for this.
OK, thanks.
--
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.
next prev parent reply other threads:[~2011-05-24 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 16:02 [Bug breakpoints/12803] New: " jan.kratochvil at redhat dot com
2011-05-24 16:36 ` [Bug breakpoints/12803] " keiths at redhat dot com
2011-05-24 16:52 ` jan.kratochvil at redhat dot com [this message]
2011-05-24 17:05 ` keiths at redhat dot com
2011-05-24 19:02 ` jan.kratochvil at redhat dot com
2011-05-24 21:00 ` cvs-commit at gcc dot gnu.org
2011-05-24 21:01 ` cvs-commit at gcc dot gnu.org
2011-05-25 0:30 ` keiths at redhat dot com
2011-07-02 19:35 ` cvs-commit at gcc dot gnu.org
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-12803-4717-XQtT9SKB1O@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).