From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Fix crash if connection drops in scoped_restore_current_thread's ctor
Date: Sat, 11 Jul 2020 00:02:55 +0100 [thread overview]
Message-ID: <af02599a-704b-934b-1153-1ddbf172d252@palves.net> (raw)
In-Reply-To: <20200708233125.1030-1-pedro@palves.net>
On 7/9/20 12:31 AM, Pedro Alves wrote:
> (I have internet again: found a sim card of a different operator that
> works. This will do until the communications tower near me is
> repaired and get I fiber back...)
>
> This series fixes the crashes exposed by the
> gdb.multi/multi-target.exp testcase when run against an Asan-enabled
> GDB build, initially reported by Simon here:
>
> https://sourceware.org/pipermail/gdb-patches/2020-July/170222.html
>
> The first two patches fix the crashes, and we should probably put them
> in GDB 10.
>
> The last patch is a follow up that avoids swallowing exceptions in
> scoped_restore_current_thread's dtor that I'm thinking would be a bit
> too invasive to put in GDB 10, I think it could do with a longer
> baking period in master.
>
> Pedro Alves (3):
> Fix crash if connection drops in scoped_restore_current_thread's ctor,
> part 1
> Fix crash if connection drops in scoped_restore_current_thread's ctor,
> part 2
> Make scoped_restore_current_thread's cdtors exception free (RFC)
I've now merged patches 1 and 2. Patch 3 will wait until after the branch
is cut.
next prev parent reply other threads:[~2020-07-10 23:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 23:31 Pedro Alves
2020-07-08 23:31 ` [PATCH 1/3] Fix crash if connection drops in scoped_restore_current_thread's ctor, part 1 Pedro Alves
2020-07-09 3:17 ` Simon Marchi
2020-07-09 10:51 ` Pedro Alves
2020-07-09 14:13 ` Simon Marchi
2020-07-08 23:31 ` [PATCH 2/3] Fix crash if connection drops in scoped_restore_current_thread's ctor, part 2 Pedro Alves
2020-07-09 3:31 ` Simon Marchi
2020-07-09 11:12 ` Pedro Alves
2020-07-09 14:16 ` Simon Marchi
2020-07-09 17:23 ` Pedro Alves
2020-07-09 17:28 ` Simon Marchi
2020-07-08 23:31 ` [PATCH 3/3] Make scoped_restore_current_thread's cdtors exception free (RFC) Pedro Alves
2020-07-09 3:49 ` Simon Marchi
2020-07-09 11:56 ` Pedro Alves
2020-07-09 12:09 ` Pedro Alves
2020-07-09 15:40 ` Simon Marchi
2020-07-09 22:22 ` Pedro Alves
2020-07-10 2:55 ` Simon Marchi
2020-10-30 1:13 ` Pedro Alves
2020-10-30 1:37 ` [pushed] Move lookup_selected_frame to frame.c Pedro Alves
2020-10-30 7:44 ` [PATCH 3/3] Make scoped_restore_current_thread's cdtors exception free (RFC) Aktemur, Tankut Baris via Gdb-patches
2020-10-30 11:32 ` Pedro Alves
2020-10-31 14:35 ` [PATCH] Fix frame cycle detection (Re: [PATCH 3/3] Make scoped_restore_current_thread's cdtors exception free (RFC)) Pedro Alves
2020-11-09 14:05 ` Aktemur, Tankut Baris via Gdb-patches
2020-11-16 13:48 ` Tom de Vries
2020-11-16 14:57 ` Pedro Alves
2020-07-10 23:02 ` Pedro Alves [this message]
2020-07-22 19:37 ` [PATCH 0/3] Fix crash if connection drops in scoped_restore_current_thread's ctor Simon Marchi
2020-07-22 20:37 ` Pedro Alves
2020-07-22 20:47 ` Simon Marchi
2020-07-23 15:28 ` [pushed] Don't touch frame_info objects if frame cache was reinitialized (was: Re: [PATCH 0/3] Fix crash if connection drops in scoped_restore_current_thread's ctor) 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=af02599a-704b-934b-1153-1ddbf172d252@palves.net \
--to=pedro@palves.net \
--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