From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 00/10] Step over thread exit (PR gdb/27338)
Date: Tue, 13 Jul 2021 16:08:07 +0100 [thread overview]
Message-ID: <6808ea55-ad84-91b3-619e-f98211c8cc9c@palves.net> (raw)
In-Reply-To: <bf22d386-d00c-4d36-01b0-785e36d9c790@palves.net>
Hi Andrew,
On 2021-07-05 12:43 p.m., Pedro Alves wrote:
> On 2021-07-05 9:42 a.m., Andrew Burgess wrote:
>> I'm a little short on time right now, so haven't looked through this
>> series in depth yet. I don't think there's much overlap, but this is
>> clearly related:
>>
>> https://sourceware.org/pipermail/gdb-patches/2021-June/180517.html
>>
>> I just wanted to make sure you'd seen this.
>
> Thanks. Hmm, I think there's actually a lot of overlap. This series
> makes the server report thread events when stepping exactly to avoid
> issuing QThreadEvents, while your series issues the QThreadEvents anyhow.
>
I just wanted to mention that I'm very interested in getting those of these
series in, but haven't had a chance to think much more about them since.
I'm thinking that the best course of action may be to join the two series into
one, and make sure we have a design that addresses everything. I'll like to take a
stab at it, but probably won't be able to until the second week of August
the earliest.
prev parent reply other threads:[~2021-07-13 15:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 13:01 Pedro Alves
2021-07-02 13:01 ` [PATCH 01/10] displaced step: pass down target_waitstatus instead of gdb_signal Pedro Alves
2021-07-05 22:19 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 02/10] gdb: clear step over information on thread exit (PR gdb/27338) Pedro Alves
2021-07-05 18:34 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 03/10] remote+gdbserver: stepped-thread-exited feature Pedro Alves
2021-07-02 17:13 ` Eli Zaretskii
2021-07-05 19:27 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 04/10] struct resumed_pending_vcont_info -> struct resume_info Pedro Alves
2021-07-05 19:46 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 05/10] remote_target::update_thread_list: Don't delete stepping threads Pedro Alves
2021-07-05 19:55 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 06/10] stop_all_threads: (re-)enable async before waiting for stops Pedro Alves
2021-07-05 21:32 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 07/10] Tweak gdbserver's no-resumed handling Pedro Alves
2021-07-05 21:51 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 08/10] Implement stepped-thread-exited feature on native+gdbserver Linux Pedro Alves
2021-07-02 13:01 ` [PATCH 09/10] lib/my-syscalls.S: Refactor new SYSCALL macro Pedro Alves
2021-07-05 22:11 ` Simon Marchi
2021-07-02 13:01 ` [PATCH 10/10] Testcases for stepping over thread exit syscall (PR gdb/27338) Pedro Alves
2021-07-05 8:42 ` [PATCH 00/10] Step over thread exit " Andrew Burgess
2021-07-05 11:43 ` Pedro Alves
2021-07-13 15:08 ` 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=6808ea55-ad84-91b3-619e-f98211c8cc9c@palves.net \
--to=pedro@palves.net \
--cc=andrew.burgess@embecosm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).