From: Xavier Roirand <roirand@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA v3] enable/disable sub breakpoint range
Date: Tue, 03 Oct 2017 16:06:00 -0000 [thread overview]
Message-ID: <e6d4b689-d4bd-e984-dd2a-56193f859a46@adacore.com> (raw)
In-Reply-To: <a79013c5-c85d-f842-2142-13b06ed2ba43@redhat.com>
Le 10/3/17 à 6:02 PM, Pedro Alves a écrit :
> On 10/03/2017 03:50 PM, Eli Zaretskii wrote:
>>> From: Xavier Roirand <roirand@adacore.com>
>>> Date: Tue, 3 Oct 2017 12:26:49 +0200
>>>
>>> This patch allows enable/disable a range of breakpoint locations
>>> using syntax:
>>>
>>> <breakpoint_number>.<first_location_number>-<last_location_number>
>>>
>>> with inclusive last_location_number.
>>>
>>> For instance, if adding a breakpoint to foo() generates 5 breakpoint
>>> locations from 1.1 to 1.5 then it's now possible to enable/disable
>>> only location breakpoint 1.3 to location breakpoint 1.5
>>> (so 1.3, 1.4 and 1.5) using syntax:
>>>
>>> enable 1.3-5 or disable 1.3-5
>>
>> What if I have, in addition to the 1.1-1.5 breakpoints also
>> breakpoints 4, 5, and 6 -- how do I disable 1.3, 1.4, 1.5, 4, and 5?
>> Do I have to say something like "disable 1.3-5.0"?
>
> I hope not. Supposedly you could do it with:
>
> (gdb) delete 1.3 1.4 1.5 4 5
>
> or:
>
> (gdb) delete 1-5 4-5
>
Yes that's how it is supposed to be used.
next prev parent reply other threads:[~2017-10-03 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 10:26 Xavier Roirand
2017-10-03 14:50 ` Eli Zaretskii
2017-10-03 16:02 ` Pedro Alves
2017-10-03 16:05 ` Pedro Alves
2017-10-03 16:06 ` Xavier Roirand [this message]
2017-10-03 16:34 ` Eli Zaretskii
2017-10-03 16:40 ` Pedro Alves
2017-10-03 17:00 ` Eli Zaretskii
2017-10-03 17:15 ` Pedro Alves
2017-10-03 18:32 ` Eli Zaretskii
2017-10-06 8:54 ` Xavier Roirand
2017-10-16 22:21 ` Philippe Waroquiers
2017-10-20 12:17 ` Xavier Roirand
2017-10-20 14:41 ` Pedro Alves
2017-10-20 14:58 ` Pedro Alves
[not found] ` <c1310ac2-b958-f0b6-aabd-5f14f8524b79@adacore.com>
2017-10-23 10:25 ` [RFA v4] " Pedro Alves
2017-10-23 11:07 ` Xavier Roirand
2017-10-26 13:11 ` 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=e6d4b689-d4bd-e984-dd2a-56193f859a46@adacore.com \
--to=roirand@adacore.com \
--cc=gdb-patches@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