From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>, Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Fix assert in delete_breakpoint
Date: Wed, 29 Nov 2023 21:46:52 +0100 [thread overview]
Message-ID: <0aeedcb1-fa72-42ba-9e84-8e39b2e73a93@suse.de> (raw)
In-Reply-To: <dec3e37b-86ab-42e7-b101-d8958ff3d288@suse.de>
On 11/29/23 13:08, Tom de Vries wrote:
> Hi,
>
> just to mention, in case I'm the only one who can reproduce this
> assertion failure, I've attached a patch to the PR (
> https://sourceware.org/bugzilla/show_bug.cgi?id=31061#c4 ) that
> implements software single step on amd64 sufficiently for the test-case
> (with some modifications to make sure software single step is being used
> when the SIGTERM arrives) to reproduce it.
>
Now somewhat more structured, and submitted as RFC (
https://sourceware.org/pipermail/gdb-patches/2023-November/204624.html ).
Thanks,
- Tom
next prev parent reply other threads:[~2023-11-29 20:46 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
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 [this message]
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=0aeedcb1-fa72-42ba-9e84-8e39b2e73a93@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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).