From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, Simon Marchi <simark@simark.ca>,
Kevin Buettner <kevinb@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v3 0/7] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error
Date: Tue, 10 Jan 2023 15:19:36 +0000 [thread overview]
Message-ID: <51c077b4-f2e2-58f4-9ca9-8a556e67d3e7@palves.net> (raw)
In-Reply-To: <5c14a49e-0ed4-f99d-17f7-c89dffd9f68a@suse.de>
Hi,
On 2023-01-05 1:35 p.m., Tom de Vries wrote:
> On 7/20/22 03:53, Simon Marchi via Gdb-patches wrote:
>>
>>
>> On 2022-02-26 19:00, Kevin Buettner via Gdb-patches wrote:
>>> This series addresses Pedro's concerns regarding the v2 series posted
>>> last year:
>>>
>>> https://sourceware.org/pipermail/gdb-patches/2021-August/181575.html
>>>
>>> In particular, it introduces a new exception which will be thrown
>>> when GDB receives a SIGTERM. That exception is handled at the
>>> top level when possible, though for the extension languages, Python
>>> and Guile, a somewhat different approach had to be taken. In order to
>>> ensure that this new exception isn't inadvertently swallowed on its
>>> way up to the top level, I also did an audit of the try / catch code
>>> involving gdb_exception, making adjustments where necessary.
>>
>> I started to look at a gdb.base/gdb-sigterm.exp failure, searched the
>> list for mentions of that test, and found this series which I think
>> addresses exactly the failure I am seeing. I'm just mentioning this to
>> bump the thread :).
>
> Hi,
>
> likewise bumping the thread, and noting that the series can claim to fix PR https://sourceware.org/bugzilla/show_bug.cgi?id=26761 .
>
I'm taking a look at this one.
> Thanks,
> - Tom
prev parent reply other threads:[~2023-01-10 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 0:00 Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 1/7] Introduce gdb_exception_forced_quit Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 2/7] Handle gdb SIGTERM by throwing / catching gdb_exception_force_quit Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 3/7] Catch gdb_exception_error instead of gdb_exception (in many places) Kevin Buettner
2022-03-03 21:11 ` Pedro Alves
2022-02-27 0:00 ` [PATCH v3 4/7] Python QUIT processing updates Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 5/7] Guile " Kevin Buettner
2022-02-27 0:00 ` [PATCH v3 6/7] QUIT processing w/ explicit throw for gdb_exception_forced_quit Kevin Buettner
2022-03-03 21:26 ` Pedro Alves
2022-02-27 0:00 ` [PATCH v3 7/7] Handle QUIT processing in the scoped_switch_fork_info destructor Kevin Buettner
2022-07-20 1:53 ` [PATCH v3 0/7] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error Simon Marchi
2023-01-05 13:35 ` Tom de Vries
2023-01-10 15:19 ` 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=51c077b4-f2e2-58f4-9ca9-8a556e67d3e7@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simark@simark.ca \
--cc=tdevries@suse.de \
/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).