From: "Alex Bennée" <alex.bennee@linaro.org>
To: Roque Arcudia Hernandez <roqueh@google.com>
Cc: richard.henderson@linaro.org, pbonzini@redhat.com,
philmd@linaro.org, slongfield@google.com, komlodi@google.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] gdbstub: Fix wrong CPUState pointer in breakpoint functions
Date: Fri, 04 Oct 2024 21:46:23 +0100 [thread overview]
Message-ID: <87v7y71tr4.fsf@draig.linaro.org> (raw)
In-Reply-To: <20240906225451.1039718-2-roqueh@google.com> (Roque Arcudia Hernandez's message of "Fri, 6 Sep 2024 15:54:50 -0700")
Roque Arcudia Hernandez <roqueh@google.com> writes:
> In the context of using the remote gdb with multiple
> processes/inferiors (multiple cluster machine) a given breakpoint
> will target an specific inferior. If needed the remote protocol will
> use the packet 'H op thread-id' with op = 'g' to change focus to the
> inferior we want to insert/remove the breakpoint to, for instance
> 'Hgp3.3' and not 'Hcp3.3'.
>
> This is supported by the documentation of the H packets:
>
> > 'H op thread-id'
> > Set thread for subsequent operations ('m', 'M', 'g', 'G',
> > et.al.). Depending on the operation to be performed, op should be
> > 'c' for step and continue operations (note that this is
> > deprecated, supporting the 'vCont' command is a better option),
> > and 'g' for other operations.
Can we better comment:
CPUState *c_cpu; /* current CPU for step/continue ops */
CPUState *g_cpu; /* current CPU for other ops */
in GDBState?
>
> This can also be verified in the GDB source code file gdb/remote.c.
> Functions remote_target::insert_breakpoint and
> remote_target::remove_breakpoint will eventually call
> remote_target::set_general_thread if it needs to change the process
> focus and not remote_target::set_continue_thread.
>
> This can be seen around a comment that says:
>
> /* Make sure the remote is pointing at the right process, if
> necessary. */
>
> Google-Bug-Id: 355027002
> Signed-off-by: Roque Arcudia Hernandez <roqueh@google.com>
> ---
> gdbstub/gdbstub.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gdbstub/gdbstub.c b/gdbstub/gdbstub.c
> index d08568cea0..98574eba68 100644
> --- a/gdbstub/gdbstub.c
> +++ b/gdbstub/gdbstub.c
> @@ -1148,7 +1148,7 @@ static void handle_insert_bp(GArray *params, void *user_ctx)
> return;
> }
>
> - res = gdb_breakpoint_insert(gdbserver_state.c_cpu,
> + res = gdb_breakpoint_insert(gdbserver_state.g_cpu,
> gdb_get_cmd_param(params, 0)->val_ul,
> gdb_get_cmd_param(params, 1)->val_ull,
> gdb_get_cmd_param(params, 2)->val_ull);
> @@ -1172,7 +1172,7 @@ static void handle_remove_bp(GArray *params, void *user_ctx)
> return;
> }
>
> - res = gdb_breakpoint_remove(gdbserver_state.c_cpu,
> + res = gdb_breakpoint_remove(gdbserver_state.g_cpu,
> gdb_get_cmd_param(params, 0)->val_ul,
> gdb_get_cmd_param(params, 1)->val_ull,
> gdb_get_cmd_param(params, 2)->val_ull);
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-10-04 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 22:54 [PATCH 0/2] Fix for multi-process gdbstub breakpoints Roque Arcudia Hernandez
2024-09-06 22:54 ` [PATCH 1/2] gdbstub: Fix wrong CPUState pointer in breakpoint functions Roque Arcudia Hernandez
2024-10-04 20:46 ` Alex Bennée [this message]
2024-10-17 15:34 ` Roque Arcudia Hernandez
2024-10-07 20:06 ` Philippe Mathieu-Daudé
2024-10-16 17:00 ` Roque Arcudia Hernandez
2024-09-06 22:54 ` [PATCH 2/2] gdbstub: Apply breakpoints only to the selected PID Roque Arcudia Hernandez
2024-10-07 10:15 ` Alex Bennée
2024-10-17 15:36 ` Roque Arcudia Hernandez
-- strict thread matches above, loose matches on Subject: below --
2025-05-08 22:45 [PATCH 0/2] Fix for multi-process gdbstub breakpoints Nabih Estefan
2025-05-08 22:45 ` [PATCH 1/2] gdbstub: Fix wrong CPUState pointer in breakpoint functions Nabih Estefan
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=87v7y71tr4.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=komlodi@google.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=roqueh@google.com \
--cc=slongfield@google.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 NNTP newsgroup(s).