From: Andrew Burgess <aburgess@redhat.com>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 01/31] displaced step: pass down target_waitstatus instead of gdb_signal
Date: Thu, 16 Mar 2023 16:07:54 +0000 [thread overview]
Message-ID: <87zg8cel2d.fsf@redhat.com> (raw)
In-Reply-To: <d24bee85-dbe3-099c-5ba4-7913f132eeb2@palves.net>
Pedro Alves <pedro@palves.net> writes:
> On 2023-02-03 10:44 a.m., Andrew Burgess wrote:
>> Pedro Alves <pedro@palves.net> writes:
>>
>>> This commit tweaks displaced_step_finish & friends to pass down a
>>> target_waitstatus instead of a gdb_signal. This needed because a
>>
>> missing word: "This IS needed".
>
> Fixed.
>
>>> @@ -5699,7 +5696,7 @@ handle_inferior_event (struct execution_control_state *ecs)
>>> has been done. Perform cleanup for parent process here. Note
>>> that this operation also cleans up the child process for vfork,
>>> because their pages are shared. */
>>> - displaced_step_finish (ecs->event_thread, GDB_SIGNAL_TRAP);
>>> + displaced_step_finish (ecs->event_thread, ecs->ws);
>>
>> This change is interesting.
>>
>> If I understand the code correctly, this call will eventually end up in
>> displaced_step_buffers::finish (displaced-stepping.c), which in turn
>> calls displaced_step_instruction_executed_successfully.
>>
>> Previously, we always passed GDB_SIGNAL_TRAP here, which (if we ignore
>> the watchpoint check in
>> displaced_step_instruction_executed_successfully) means that
>> displaced_step_instruction_executed_successfully would always return
>> true, and then displaced_step_buffers::finish would call
>> gdbarch_displaced_step_fixup.
>>
>> After this change, we know that esc->ws.kind is either
>> TARGET_WAITKIND_FORKED or TARGET_WAITKIND_VFORKED, so we know that
>> displaced_step_instruction_executed_successfully will always return
>> false, and displaced_step_buffers::finish will no longer call
>> gdbarch_displaced_step_fixup.
>>
>
> Good catch!
>
> I was tweaking the change to address your comment, and was coming to the
> conclusion that what I really wanted was this:
>
> static bool
> displaced_step_instruction_executed_successfully
> (gdbarch *arch, const target_waitstatus &status)
> {
> if (status.kind () == TARGET_WAITKIND_STOPPED
> && status.sig () != GDB_SIGNAL_TRAP)
> return false;
>
> /* All other waitkinds can only happen if the instruction fully
> executed. For example, a fork, or a syscall entry can only
> happen if the syscall instruction actually executed. */
>
> (the comment is new)
>
> And then, I remembered, I actually wrote that early if like that originally,
> and I changed it in response to this review:
>
> https://inbox.sourceware.org/gdb-patches/44f74af8-248b-1af8-3612-980c08607bf4@simark.ca/
>
> The review was totally right, it was my response that was misguided.
>
> But I'm confused because I am pretty sure that I wrote a reply to that
> message, saying that I did not intend to change the behavior, so I'd "fix" it.
> I can't find it in my outbox either, I guess I erroneously canceled my
> email window instead of sending the message...
>
> Anyhow, looks like I made it worse while trying to address Simon's comment. :-P
>
> So I think I should go back to what I had, like before, and my response
> to Simon should have been instead:
>
> - yes, the change is intended. If we stopped for an event other than
> TARGET_WAITKIND_STOPPED, like for instance, TARGET_WAITKIND_FORKED,
> TARGET_WAITKIND_SYSCALL_ENTRY, then it must be that the instruction
> executed successfully, otherwise the syscall wouldn't have triggered.
>
>> What I don't understand well enough is what this actually means for a
>> running inferior.
>>
>> It's odd because the comment in infrun.c (just above your change)
>> indicates that to get to this point the displaced step must have
>> completed successfully, while after this change, the new code path in
>> displaced_step_buffers::finish indicates we believe the displaced step
>> didn't complete successfully:
>>
>> /* Since the instruction didn't complete, all we can do is relocate the
>> PC. */
>>
>> Do you know if any of our test cases hit this path?
>>
>
> I know that you posted a series for this, which I plan to take a good look
> at (I actually planned on doing that earlier this week, but I had a couple
> major distractions, sorry).
>
> WDYT of the version below?
I took a look through and I'm happy with it. But I would like you to
consider holding off until my displaced step patch has some feedback.
I'm currently rebasing the patch. My patch deletes
displaced_step_instruction_executed_successfully, which I realised makes
passing the signal (or now target_waitstatus) redundant. As such I'm
just testing an additional patch in the series which touches every place
you're touching - but removes the signal instead of changing it.
I hope to post my updated series later today (once testing completes).
Thanks,
Andrew
>
> From 0ccfd6822ef83eddb48c6f7bf21533858f177bc9 Mon Sep 17 00:00:00 2001
> From: Pedro Alves <pedro@palves.net>
> Date: Tue, 22 Jun 2021 15:42:51 +0100
> Subject: [PATCH] displaced step: pass down target_waitstatus instead of
> gdb_signal
>
> This commit tweaks displaced_step_finish & friends to pass down a
> target_waitstatus instead of a gdb_signal. This is needed because a
> patch later in the series will want to make
> displaced_step_buffers::finish handle TARGET_WAITKIND_THREAD_EXITED.
> It also helps with the TARGET_WAITKIND_THREAD_CLONED patch later in
> the series.
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27338
> Change-Id: I4c5d338647b028071bc498c4e47063795a2db4c0
> ---
> gdb/displaced-stepping.c | 16 +++++++++++-----
> gdb/displaced-stepping.h | 2 +-
> gdb/gdbarch-gen.h | 4 ++--
> gdb/gdbarch.c | 4 ++--
> gdb/gdbarch_components.py | 2 +-
> gdb/infrun.c | 17 +++++++----------
> gdb/linux-tdep.c | 5 +++--
> gdb/linux-tdep.h | 2 +-
> gdb/rs6000-tdep.c | 4 ++--
> 9 files changed, 30 insertions(+), 26 deletions(-)
>
> diff --git a/gdb/displaced-stepping.c b/gdb/displaced-stepping.c
> index 06b32a80f6a..08ae1ce4397 100644
> --- a/gdb/displaced-stepping.c
> +++ b/gdb/displaced-stepping.c
> @@ -192,12 +192,18 @@ write_memory_ptid (ptid_t ptid, CORE_ADDR memaddr,
> }
>
> static bool
> -displaced_step_instruction_executed_successfully (gdbarch *arch,
> - gdb_signal signal)
> +displaced_step_instruction_executed_successfully
> + (gdbarch *arch, const target_waitstatus &status)
> {
> - if (signal != GDB_SIGNAL_TRAP)
> + if (status.kind () == TARGET_WAITKIND_STOPPED
> + && status.sig () != GDB_SIGNAL_TRAP)
> return false;
>
> + /* All other (thread event) waitkinds can only happen if the
> + instruction fully executed. For example, a fork, or a syscall
> + entry can only happen if the syscall instruction actually
> + executed. */
> +
> if (target_stopped_by_watchpoint ())
> {
> if (gdbarch_have_nonsteppable_watchpoint (arch)
> @@ -210,7 +216,7 @@ displaced_step_instruction_executed_successfully (gdbarch *arch,
>
> displaced_step_finish_status
> displaced_step_buffers::finish (gdbarch *arch, thread_info *thread,
> - gdb_signal sig)
> + const target_waitstatus &status)
> {
> gdb_assert (thread->displaced_step_state.in_progress ());
>
> @@ -256,7 +262,7 @@ displaced_step_buffers::finish (gdbarch *arch, thread_info *thread,
> regcache *rc = get_thread_regcache (thread);
>
> bool instruction_executed_successfully
> - = displaced_step_instruction_executed_successfully (arch, sig);
> + = displaced_step_instruction_executed_successfully (arch, status);
>
> if (instruction_executed_successfully)
> {
> diff --git a/gdb/displaced-stepping.h b/gdb/displaced-stepping.h
> index e154927ad92..d2c3fc1b2b4 100644
> --- a/gdb/displaced-stepping.h
> +++ b/gdb/displaced-stepping.h
> @@ -168,7 +168,7 @@ struct displaced_step_buffers
> CORE_ADDR &displaced_pc);
>
> displaced_step_finish_status finish (gdbarch *arch, thread_info *thread,
> - gdb_signal sig);
> + const target_waitstatus &status);
>
> const displaced_step_copy_insn_closure *
> copy_insn_closure_by_addr (CORE_ADDR addr);
> diff --git a/gdb/gdbarch-gen.h b/gdb/gdbarch-gen.h
> index ddb97f60315..5805dcb75ef 100644
> --- a/gdb/gdbarch-gen.h
> +++ b/gdb/gdbarch-gen.h
> @@ -1103,8 +1103,8 @@ extern void set_gdbarch_displaced_step_prepare (struct gdbarch *gdbarch, gdbarch
>
> /* Clean up after a displaced step of THREAD. */
>
> -typedef displaced_step_finish_status (gdbarch_displaced_step_finish_ftype) (struct gdbarch *gdbarch, thread_info *thread, gdb_signal sig);
> -extern displaced_step_finish_status gdbarch_displaced_step_finish (struct gdbarch *gdbarch, thread_info *thread, gdb_signal sig);
> +typedef displaced_step_finish_status (gdbarch_displaced_step_finish_ftype) (struct gdbarch *gdbarch, thread_info *thread, const target_waitstatus &ws);
> +extern displaced_step_finish_status gdbarch_displaced_step_finish (struct gdbarch *gdbarch, thread_info *thread, const target_waitstatus &ws);
> extern void set_gdbarch_displaced_step_finish (struct gdbarch *gdbarch, gdbarch_displaced_step_finish_ftype *displaced_step_finish);
>
> /* Return the closure associated to the displaced step buffer that is at ADDR. */
> diff --git a/gdb/gdbarch.c b/gdb/gdbarch.c
> index 7e4e34d5aca..0b122a86055 100644
> --- a/gdb/gdbarch.c
> +++ b/gdb/gdbarch.c
> @@ -4096,13 +4096,13 @@ set_gdbarch_displaced_step_prepare (struct gdbarch *gdbarch,
> }
>
> displaced_step_finish_status
> -gdbarch_displaced_step_finish (struct gdbarch *gdbarch, thread_info *thread, gdb_signal sig)
> +gdbarch_displaced_step_finish (struct gdbarch *gdbarch, thread_info *thread, const target_waitstatus &ws)
> {
> gdb_assert (gdbarch != NULL);
> gdb_assert (gdbarch->displaced_step_finish != NULL);
> if (gdbarch_debug >= 2)
> gdb_printf (gdb_stdlog, "gdbarch_displaced_step_finish called\n");
> - return gdbarch->displaced_step_finish (gdbarch, thread, sig);
> + return gdbarch->displaced_step_finish (gdbarch, thread, ws);
> }
>
> void
> diff --git a/gdb/gdbarch_components.py b/gdb/gdbarch_components.py
> index caa65c334ec..8d72bff347e 100644
> --- a/gdb/gdbarch_components.py
> +++ b/gdb/gdbarch_components.py
> @@ -1878,7 +1878,7 @@ Clean up after a displaced step of THREAD.
> """,
> type="displaced_step_finish_status",
> name="displaced_step_finish",
> - params=[("thread_info *", "thread"), ("gdb_signal", "sig")],
> + params=[("thread_info *", "thread"), ("const target_waitstatus &", "ws")],
> predefault="NULL",
> invalid="(! gdbarch->displaced_step_finish) != (! gdbarch->displaced_step_prepare)",
> )
> diff --git a/gdb/infrun.c b/gdb/infrun.c
> index ab77300f1ff..99f2a8e039d 100644
> --- a/gdb/infrun.c
> +++ b/gdb/infrun.c
> @@ -1895,7 +1895,8 @@ displaced_step_prepare (thread_info *thread)
> DISPLACED_STEP_FINISH_STATUS_OK as well. */
>
> static displaced_step_finish_status
> -displaced_step_finish (thread_info *event_thread, enum gdb_signal signal)
> +displaced_step_finish (thread_info *event_thread,
> + const target_waitstatus &event_status)
> {
> displaced_step_thread_state *displaced = &event_thread->displaced_step_state;
>
> @@ -1917,7 +1918,7 @@ displaced_step_finish (thread_info *event_thread, enum gdb_signal signal)
> /* Do the fixup, and release the resources acquired to do the displaced
> step. */
> return gdbarch_displaced_step_finish (displaced->get_original_gdbarch (),
> - event_thread, signal);
> + event_thread, event_status);
> }
>
> /* Data to be passed around while handling an event. This data is
> @@ -5122,7 +5123,7 @@ handle_one (const wait_one_event &event)
> /* We caught the event that we intended to catch, so
> there's no event to save as pending. */
>
> - if (displaced_step_finish (t, GDB_SIGNAL_0)
> + if (displaced_step_finish (t, event.ws)
> == DISPLACED_STEP_FINISH_STATUS_NOT_EXECUTED)
> {
> /* Add it back to the step-over queue. */
> @@ -5137,7 +5138,6 @@ handle_one (const wait_one_event &event)
> }
> else
> {
> - enum gdb_signal sig;
> struct regcache *regcache;
>
> infrun_debug_printf
> @@ -5148,10 +5148,7 @@ handle_one (const wait_one_event &event)
> /* Record for later. */
> save_waitstatus (t, event.ws);
>
> - sig = (event.ws.kind () == TARGET_WAITKIND_STOPPED
> - ? event.ws.sig () : GDB_SIGNAL_0);
> -
> - if (displaced_step_finish (t, sig)
> + if (displaced_step_finish (t, event.ws)
> == DISPLACED_STEP_FINISH_STATUS_NOT_EXECUTED)
> {
> /* Add it back to the step-over queue. */
> @@ -5753,7 +5750,7 @@ handle_inferior_event (struct execution_control_state *ecs)
> has been done. Perform cleanup for parent process here. Note
> that this operation also cleans up the child process for vfork,
> because their pages are shared. */
> - displaced_step_finish (ecs->event_thread, GDB_SIGNAL_TRAP);
> + displaced_step_finish (ecs->event_thread, ecs->ws);
> /* Start a new step-over in another thread if there's one
> that needs it. */
> start_step_over ();
> @@ -6118,7 +6115,7 @@ resumed_thread_with_pending_status (struct thread_info *tp,
> static int
> finish_step_over (struct execution_control_state *ecs)
> {
> - displaced_step_finish (ecs->event_thread, ecs->event_thread->stop_signal ());
> + displaced_step_finish (ecs->event_thread, ecs->ws);
>
> bool had_step_over_info = step_over_info_valid_p ();
>
> diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c
> index e6ce13a1c67..036ea9f931d 100644
> --- a/gdb/linux-tdep.c
> +++ b/gdb/linux-tdep.c
> @@ -2621,13 +2621,14 @@ linux_displaced_step_prepare (gdbarch *arch, thread_info *thread,
> /* See linux-tdep.h. */
>
> displaced_step_finish_status
> -linux_displaced_step_finish (gdbarch *arch, thread_info *thread, gdb_signal sig)
> +linux_displaced_step_finish (gdbarch *arch, thread_info *thread,
> + const target_waitstatus &status)
> {
> linux_info *per_inferior = get_linux_inferior_data (thread->inf);
>
> gdb_assert (per_inferior->disp_step_bufs.has_value ());
>
> - return per_inferior->disp_step_bufs->finish (arch, thread, sig);
> + return per_inferior->disp_step_bufs->finish (arch, thread, status);
> }
>
> /* See linux-tdep.h. */
> diff --git a/gdb/linux-tdep.h b/gdb/linux-tdep.h
> index 16e1b806b26..e09a6ef32b1 100644
> --- a/gdb/linux-tdep.h
> +++ b/gdb/linux-tdep.h
> @@ -72,7 +72,7 @@ extern displaced_step_prepare_status linux_displaced_step_prepare
> /* Implementation of gdbarch_displaced_step_finish. */
>
> extern displaced_step_finish_status linux_displaced_step_finish
> - (gdbarch *arch, thread_info *thread, gdb_signal sig);
> + (gdbarch *arch, thread_info *thread, const target_waitstatus &status);
>
> /* Implementation of gdbarch_displaced_step_copy_insn_closure_by_addr. */
>
> diff --git a/gdb/rs6000-tdep.c b/gdb/rs6000-tdep.c
> index 104515de030..f9bbc435184 100644
> --- a/gdb/rs6000-tdep.c
> +++ b/gdb/rs6000-tdep.c
> @@ -1088,13 +1088,13 @@ ppc_displaced_step_prepare (gdbarch *arch, thread_info *thread,
>
> static displaced_step_finish_status
> ppc_displaced_step_finish (gdbarch *arch, thread_info *thread,
> - gdb_signal sig)
> + const target_waitstatus &status)
> {
> ppc_inferior_data *per_inferior = get_ppc_per_inferior (thread->inf);
>
> gdb_assert (per_inferior->disp_step_buf.has_value ());
>
> - return per_inferior->disp_step_buf->finish (arch, thread, sig);
> + return per_inferior->disp_step_buf->finish (arch, thread, status);
> }
>
> /* Implementation of gdbarch_displaced_step_restore_all_in_ptid. */
>
> base-commit: 2562954ede66f32bff7d985e752b8052c2ae5775
> --
> 2.36.0
next prev parent reply other threads:[~2023-03-16 16:07 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 20:30 [PATCH 00/31] Step over thread clone and thread exit Pedro Alves
2022-12-12 20:30 ` [PATCH 01/31] displaced step: pass down target_waitstatus instead of gdb_signal Pedro Alves
2023-02-03 10:44 ` Andrew Burgess
2023-03-10 17:15 ` Pedro Alves
2023-03-16 16:07 ` Andrew Burgess [this message]
2023-03-22 21:29 ` Andrew Burgess
2023-03-23 15:15 ` Pedro Alves
2023-03-27 12:40 ` Andrew Burgess
2023-03-27 16:21 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 02/31] linux-nat: introduce pending_status_str Pedro Alves
2023-02-03 12:00 ` Andrew Burgess
2023-03-10 17:15 ` Pedro Alves
2023-03-16 16:19 ` Andrew Burgess
2023-03-27 18:05 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 03/31] gdb/linux: Delete all other LWPs immediately on ptrace exec event Pedro Alves
2023-03-21 14:50 ` Andrew Burgess
2023-04-04 13:57 ` Pedro Alves
2023-04-14 19:29 ` Pedro Alves
2023-05-26 15:04 ` Andrew Burgess
2023-11-13 14:04 ` Pedro Alves
2023-05-26 14:45 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 04/31] Step over clone syscall w/ breakpoint, TARGET_WAITKIND_THREAD_CLONED Pedro Alves
2023-02-04 15:38 ` Andrew Burgess
2023-03-10 17:16 ` Pedro Alves
2023-03-21 16:06 ` Andrew Burgess
2023-11-13 14:05 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 05/31] Support clone events in the remote protocol Pedro Alves
2023-03-22 15:46 ` Andrew Burgess
2023-11-13 14:05 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 06/31] Avoid duplicate QThreadEvents packets Pedro Alves
2023-05-26 15:53 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 07/31] enum_flags to_string Pedro Alves
2023-01-30 20:07 ` Simon Marchi
2022-12-12 20:30 ` [PATCH 08/31] Thread options & clone events (core + remote) Pedro Alves
2023-01-31 12:25 ` Lancelot SIX
2023-03-10 19:16 ` Pedro Alves
2023-06-06 13:29 ` Andrew Burgess
2023-11-13 14:07 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 09/31] Thread options & clone events (native Linux) Pedro Alves
2023-06-06 13:43 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 10/31] Thread options & clone events (Linux GDBserver) Pedro Alves
2023-06-06 14:12 ` Andrew Burgess
2023-11-13 14:07 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 11/31] gdbserver: Hide and don't detach pending clone children Pedro Alves
2023-06-07 16:10 ` Andrew Burgess
2023-11-13 14:08 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 12/31] Remove gdb/19675 kfails (displaced stepping + clone) Pedro Alves
2023-06-07 17:08 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 13/31] Add test for stepping over clone syscall Pedro Alves
2023-06-07 17:42 ` Andrew Burgess
2023-11-13 14:09 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 14/31] all-stop/synchronous RSP support thread-exit events Pedro Alves
2023-06-07 17:52 ` Andrew Burgess
2023-11-13 14:11 ` Pedro Alves
2023-12-15 18:15 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 15/31] gdbserver/linux-low.cc: Ignore event_ptid if TARGET_WAITKIND_IGNORE Pedro Alves
2022-12-12 20:30 ` [PATCH 16/31] Move deleting thread on TARGET_WAITKIND_THREAD_EXITED to core Pedro Alves
2023-06-08 12:27 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 17/31] Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit Pedro Alves
2023-06-08 13:17 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 18/31] Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver Pedro Alves
2023-06-08 14:14 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 19/31] Implement GDB_THREAD_OPTION_EXIT support for native Linux Pedro Alves
2023-06-08 14:17 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 20/31] gdb: clear step over information on thread exit (PR gdb/27338) Pedro Alves
2023-06-08 15:29 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 21/31] stop_all_threads: (re-)enable async before waiting for stops Pedro Alves
2023-06-08 15:49 ` Andrew Burgess
2023-11-13 14:12 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 22/31] gdbserver: Queue no-resumed event after thread exit Pedro Alves
2023-06-08 18:16 ` Andrew Burgess
2023-11-13 14:12 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 23/31] Don't resume new threads if scheduler-locking is in effect Pedro Alves
2023-06-08 18:24 ` Andrew Burgess
2023-11-13 14:12 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 24/31] Report thread exit event for leader if reporting thread exit events Pedro Alves
2023-06-09 13:11 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 25/31] Ignore failure to read PC when resuming Pedro Alves
2023-06-10 10:33 ` Andrew Burgess
2023-11-13 14:13 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 26/31] gdb/testsuite/lib/my-syscalls.S: Refactor new SYSCALL macro Pedro Alves
2023-06-10 10:33 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 27/31] Testcases for stepping over thread exit syscall (PR gdb/27338) Pedro Alves
2023-06-12 9:53 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 28/31] Document remote clone events, and QThreadOptions packet Pedro Alves
2023-06-05 15:53 ` Andrew Burgess
2023-11-13 14:13 ` Pedro Alves
2023-06-12 12:06 ` Andrew Burgess
2023-11-13 14:15 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 29/31] inferior::clear_thread_list always silent Pedro Alves
2023-06-12 12:20 ` Andrew Burgess
2022-12-12 20:31 ` [PATCH 30/31] Centralize "[Thread ...exited]" notifications Pedro Alves
2023-02-04 16:05 ` Andrew Burgess
2023-03-10 17:21 ` Pedro Alves
2023-02-16 15:40 ` Andrew Burgess
2023-06-12 12:23 ` Andrew Burgess
2022-12-12 20:31 ` [PATCH 31/31] Cancel execution command on thread exit, when stepping, nexting, etc Pedro Alves
2023-06-12 13:12 ` Andrew Burgess
2023-01-24 19:47 ` [PATCH v3 00/31] Step over thread clone and thread exit Pedro Alves
2023-11-13 14:24 ` [PATCH " 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=87zg8cel2d.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).