Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simark@simark.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add MI "-break-insert --qualified"
Date: Sun, 13 Sep 2020 18:13:22 +0100	[thread overview]
Message-ID: <f2456582-f0cb-78fc-eb44-c7783140915d@palves.net> (raw)
In-Reply-To: <619c2383-5a76-3be2-cf80-dd532195fa30@simark.ca>

On 9/2/20 7:35 PM, Simon Marchi wrote:
> On 2020-09-01 2:07 p.m., Pedro Alves wrote:
>> Currently -break-insert always creates a wildmatching breakpoint, and
>> there's no way to ask for a fullname match.  To address that, this
>> patch adds the equivalent of "break -qualified" to MI:
>>
>>   "-break-insert --qualified".
>>
>> For the testcase, curiously, it doesn't look like we have _any_
>> testcase that tests a breakpoint with multiple locations, and, the
>> existing mi_create_breakpoint / mi_make_breakpoint procedures are only
>> good for breakpoints with a single location.  This patch thus adds a
>> few new companion routines to mi-support.exp for breakpoints with
>> multiple locations: mi_create_breakpoint_multi,
>> mi_make_breakpoint_loc, mi_make_breakpoint_multi.
> 
> The code looks good to me.
> 

Thank you both.

I've merged this now, with NEWS entry moved to the new
"Changes since GDB 10" section.

Pedro Alves


      reply	other threads:[~2020-09-13 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 18:07 Pedro Alves
2020-09-01 18:13 ` Eli Zaretskii
2020-09-02 18:35 ` Simon Marchi
2020-09-13 17:13   ` Pedro Alves [this message]

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=f2456582-f0cb-78fc-eb44-c7783140915d@palves.net \
    --to=pedro@palves.net \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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