From: Pedro Alves <palves@redhat.com>
To: Keith Seitz <keiths@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2.1 2/3] Make "break foo" find "A::foo", A::B::foo", etc. [C++ and wild matching]
Date: Wed, 29 Nov 2017 19:52:00 -0000 [thread overview]
Message-ID: <c6666ae1-8cf0-b406-0e73-a80edf114f69@redhat.com> (raw)
In-Reply-To: <548d66d2-d47c-d2c1-174e-d224ae297e7a@redhat.com>
On 11/28/2017 05:35 PM, Keith Seitz wrote:
> On 11/28/2017 04:39 AM, Pedro Alves wrote:
>>
>> Alright, let me know what think of the above.
>
> I was just seeking a sanity check (*my* sanity). This is a similar situation to explicit locations. Not every `interface' has access to those yet, either.
>
> So, please, don't hesitate to push this!
Yeah, I'm a bit hesitant, since I consider this a big
change. :-) But I asked around on IRC to double-check
if anyone had last-minute comments, and everyone seemed
pretty cool about it, so I pushed it in now. Hurray!
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-11-29 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 17:13 [PATCH v2 0/3] C++ debugging improvements: wild matching and ABI tags Pedro Alves
2017-11-27 17:13 ` [PATCH v2 3/3] Breakpoints in symbols with ABI tags (PR c++/19436) Pedro Alves
2017-11-28 3:47 ` Keith Seitz
2017-11-27 17:13 ` [PATCH v2 1/3] Handle custom completion match prefix / LCD Pedro Alves
2017-11-28 1:42 ` Keith Seitz
2017-11-27 17:14 ` [PATCH v2 2/3] Make "break foo" find "A::foo", A::B::foo", etc. [C++ and wild matching] Pedro Alves
2017-11-27 17:47 ` Eli Zaretskii
2017-11-28 0:01 ` Pedro Alves
2017-11-28 0:14 ` [PATCH v2.1 " Pedro Alves
2017-11-28 2:50 ` Keith Seitz
2017-11-28 12:39 ` Pedro Alves
2017-11-28 17:35 ` Keith Seitz
2017-11-29 19:52 ` Pedro Alves [this message]
2017-11-27 17:33 ` [PATCH v2 0/3] C++ debugging improvements: wild matching and ABI tags Pedro Alves
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=c6666ae1-8cf0-b406-0e73-a80edf114f69@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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