From: Pedro Alves <pedro@palves.net>
To: Enze Li <lienze2010@hotmail.com>, tom@tromey.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb: fix using clear command to delete non-user breakpoints(PR cli/7161)
Date: Fri, 22 Apr 2022 16:01:49 +0100 [thread overview]
Message-ID: <24ba3cf3-20d6-e864-9c4a-85287c55a2ac@palves.net> (raw)
In-Reply-To: <MEAP282MB029307AD5CC6CF2093437D00DDF29@MEAP282MB0293.AUSP282.PROD.OUTLOOK.COM>
On 2022-04-19 15:07, Enze Li wrote:
>> Not a strong requirement, but it would be great if we also had a test
>> trying to clear an internal
>> python breakpoint. Did you look into adding that? If it's too
>> complicated to add it here or to
>> a new file, maybe add a "clear" test to gdb.python/py-breakpoint.exp
>> ?
> If this is a requirement, I'd like to implement it. Is this something
> that can be done later?
Yes, certainly.
>
> I've sent a fix patch to the gdb-patch@list and I posted it here:
> https://sourceware.org/pipermail/gdb-patches/2022-April/188044.html
next prev parent reply other threads:[~2022-04-22 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220314122406.24889-1-lienze2010@hotmail.com>
2022-03-17 14:24 ` [PATCH v2] " Enze Li
2022-03-23 14:25 ` Enze Li
2022-04-14 5:58 ` [PING^2][PATCH " Enze Li
2022-04-15 16:41 ` [PATCH " Tom Tromey
2022-04-16 3:42 ` [PATCH v3] " Enze Li
2022-04-17 21:26 ` Tom Tromey
2022-04-18 16:04 ` Pedro Alves
2022-04-19 14:07 ` Enze Li
2022-04-22 15:01 ` Pedro Alves [this message]
2022-04-18 16:12 ` Tom Tromey
2022-04-19 2:10 ` Enze Li
2022-04-19 3:26 ` Tom Tromey
2022-04-18 23:49 ` Simon Marchi
2022-04-19 3:37 ` Simon Marchi
2022-04-19 13:32 ` Enze Li
2022-04-17 7:18 ` [PATCH RESEND " Enze Li
2022-04-17 22:29 ` Lancelot SIX
2022-04-21 14:29 ` Enze Li
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=24ba3cf3-20d6-e864-9c4a-85287c55a2ac@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=lienze2010@hotmail.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).