From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Fix assert in delete_breakpoint
Date: Wed, 15 Nov 2023 13:12:27 +0100 [thread overview]
Message-ID: <96bc9fec-6f2d-488a-b52e-2a987cf47d2c@suse.de> (raw)
In-Reply-To: <ad47339b-e8b1-4cda-8c66-830919024ebf@suse.de>
On 11/15/23 12:12, Tom de Vries wrote:
> Because it's deleted twice.
Just to confirm this theory, I added this patch:
...
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index fe09dbcbeee..12a3a2260d7 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -12583,6 +12583,8 @@ void
delete_breakpoint (struct breakpoint *bpt)
{
gdb_assert (bpt != NULL);
+ fprintf (stderr, "delete_breakpoint: %p\n", bpt);
+ fflush (stderr);
/* Has this bp already been deleted? This can happen because
multiple lists can hold pointers to bp's. bpstat lists are
...
and got:
...
[infrun] handle_signal_stop: [17091.17091.0] hit its single-step
breakpoint^M
delete_breakpoint: 0xabc756a8^M
delete_breakpoint: 0xabc756a8^M
/home/rock/gdb/src/gdb/../gdbsupport/intrusive_list.h:458:
internal-error: erase_element: Assertion `elem_node->prev \
!= INTRUSIVE_LIST_UNLINKED_VALUE' failed.^M
...
Thanks,
- Tom
next prev parent reply other threads:[~2023-11-15 12:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 15:26 Tom de Vries
2023-11-14 15:09 ` Simon Marchi
2023-11-15 11:12 ` Tom de Vries
2023-11-15 12:12 ` Tom de Vries [this message]
2023-11-21 12:22 ` Tom de Vries
2023-11-21 16:11 ` Simon Marchi
2023-11-21 16:52 ` Tom de Vries
2023-11-22 12:44 ` Tom de Vries
2023-11-22 14:49 ` Tom de Vries
2023-11-27 10:19 ` Tom de Vries
2023-11-27 16:29 ` Simon Marchi
2023-11-28 15:22 ` Tom de Vries
2023-11-28 15:30 ` Tom Tromey
2023-11-29 12:08 ` Tom de Vries
2023-11-29 20:46 ` Tom de Vries
2023-11-29 21:33 ` Tom de Vries
2023-11-30 17:08 ` Simon Marchi
2023-11-21 16:40 ` Luis Machado
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=96bc9fec-6f2d-488a-b52e-2a987cf47d2c@suse.de \
--to=tdevries@suse.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).