From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RESEND][PATCH] gdbstub: Add vCont support
Date: Thu, 15 Jan 2009 14:32:53 -0600 [thread overview]
Message-ID: <496F9D75.4020802@codemonkey.ws> (raw)
In-Reply-To: <496DFA33.2020606@siemens.com>
Jan Kiszka wrote:
> [ Also available via git://git.kiszka.org/qemu.git queue/gdb ]
>
> In order to set the VCPU for the next single-step command, you need gdb
> 6.8 or better - and this patch. It enhances the existing support for
> representing VCPUs as threads to the gdb frontend by introducing the
> vCont remote gdb command. This is used by gdb to switch the debugging
> focus for single-stepping multi-threaded targets.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
I think the consensus from the last posting of this was that modeling
threads was pretty broken and that we should model as processes. Did I
miss something there?
Regards,
Anthony Liguori
> ---
>
> gdbstub.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 56 insertions(+), 0 deletions(-)
>
> diff --git a/gdbstub.c b/gdbstub.c
> index 0bcd5d5..1cb20b7 100644
> --- a/gdbstub.c
> +++ b/gdbstub.c
> @@ -1542,6 +1542,62 @@ static int gdb_handle_packet(GDBState *s, const char *line_buf)
> s->signal = 0;
> gdb_continue(s);
> return RS_IDLE;
> + case 'v':
> + if (strncmp(p, "Cont", 4) == 0) {
> + int res_signal, res_thread;
> +
> + p += 4;
> + if (*p == '?') {
> + put_packet(s, "vCont;c;C;s;S");
> + break;
> + }
> + res = 0;
> + res_signal = 0;
> + res_thread = 0;
> + while (*p) {
> + int action, signal;
> +
> + if (*p++ != ';') {
> + res = 0;
> + break;
> + }
> + action = *p++;
> + signal = 0;
> + if (action == 'C' || action == 'S')
> + signal = strtoul(p, (char **)&p, 16);
> + else if (action != 'c' && action != 's') {
> + res = 0;
> + break;
> + }
> + thread = 0;
> + if (*p == ':')
> + thread = strtoull(p+1, (char **)&p, 16);
> +
> + action = tolower(action);
> + if (res == 0 || (res == 'c' && action == 's')) {
> + res = action;
> + res_signal = signal;
> + res_thread = thread;
> + }
> + }
> + if (res) {
> + if (res_thread != -1 && res_thread != 0) {
> + for (env = first_cpu; env != NULL; env = env->next_cpu)
> + if (env->cpu_index + 1 == res_thread)
> + break;
> + if (env == NULL) {
> + put_packet(s, "E22");
> + break;
> + }
> + s->c_cpu = env;
> + }
> + if (res == 's')
> + cpu_single_step(s->c_cpu, sstep_flags);
> + gdb_continue(s);
> + return RS_IDLE;
> + }
> + break;
> + }
> case 'k':
> /* Kill the target */
> fprintf(stderr, "\nQEMU: Terminated via GDBstub\n");
>
>
>
next prev parent reply other threads:[~2009-01-15 20:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 14:44 [Qemu-devel] [RESEND][PATCH] gdbstub: Add vCont support Jan Kiszka
2009-01-14 15:03 ` Krumme, Chris
2009-01-14 16:30 ` [Qemu-devel] " Jan Kiszka
2009-01-15 20:32 ` Anthony Liguori [this message]
2009-01-15 21:27 ` Jan Kiszka
2009-01-16 0:15 ` Paul Brook
2009-01-16 8:05 ` Jan Kiszka
2009-01-16 8:38 ` Jan Kiszka
2009-01-16 17:05 ` Paul Brook
2009-01-16 19:25 ` Jan Kiszka
2009-01-16 20:42 ` Daniel Jacobowitz
2009-01-17 10:03 ` Jamie Lokier
2009-01-17 17:33 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2009-03-10 17:21 [Qemu-devel] " Jan Kiszka
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=496F9D75.4020802@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).