qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] gdbstub improvements for gdb kill/detach/quit
Date: Mon, 12 May 2008 13:29:28 +0200	[thread overview]
Message-ID: <20080512112928.GC21455@edgar.se.axis.com> (raw)
In-Reply-To: <482456EA.8020108@windriver.com>

On Fri, May 09, 2008 at 08:51:38AM -0500, Jason Wessel wrote:
> Attached is a patch to improve the gdb stub 'D' 'k' and '?' packets. 
> See the patch header for details.
> 
> Jason.

> From: Jason Wessel <jason.wessel@windriver.com>
> Subject: [PATCH] support for gdb "detach/kill/quit"
> 
> Implement the 'k' gdbserial packet which kills the qemu instance via
> the debugger stub.
> 
> Implement the 'D' detach packet for the gdb stub such that you can
> disconnect gdb with the "detach" command.  This required implementing
> a cpu_breakpoint_remove_all function to cleanup all the breakpoints
> prior to leaving the gdb stub else simulation can stop with no
> debugger attached.
> 
> On a '?' packet remove all the breakpoints.  This is considered more
> of a safety net in case you force killed gdb or it crashed and you are
> reconnecting.  The identical behavior exists for kgdb in the linux
> kernel.
> 
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>

Thanks, a few comments inlined.

> ---
>  cpu-all.h |    1 +
>  exec.c    |   14 ++++++++++++++
>  gdbstub.c |   16 ++++++++++++++++
>  3 files changed, 31 insertions(+)
> 
> --- a/cpu-all.h
> +++ b/cpu-all.h
> @@ -759,6 +759,7 @@ void cpu_interrupt(CPUState *s, int mask
>  void cpu_reset_interrupt(CPUState *env, int mask);
>  
>  int cpu_watchpoint_insert(CPUState *env, target_ulong addr);
> +int cpu_breakpoint_remove_all(CPUState *env);
>  int cpu_watchpoint_remove(CPUState *env, target_ulong addr);
>  int cpu_breakpoint_insert(CPUState *env, target_ulong pc);
>  int cpu_breakpoint_remove(CPUState *env, target_ulong pc);
> --- a/gdbstub.c
> +++ b/gdbstub.c
> @@ -901,6 +901,11 @@ static int gdb_handle_packet(GDBState *s
>          /* TODO: Make this return the correct value for user-mode.  */
>          snprintf(buf, sizeof(buf), "S%02x", SIGTRAP);
>          put_packet(s, buf);
> +        /* Remove all the breakpoints when this query is issued,
> +         * because gdb is doing and initial connect and the state
> +         * should be cleaned up. 
> +         */
> +        cpu_breakpoint_remove_all(env);
>          break;
>      case 'c':
>          if (*p != '\0') {
> @@ -924,6 +929,17 @@ static int gdb_handle_packet(GDBState *s
>          }
>          gdb_continue(s);
>  	return RS_IDLE;
> +    case 'k':
> +        /* Kill the target */
> +        fprintf(stderr, "\nQEMU: Terminated via GDBstub\n");
> +        exit(0);



Should we consider qemu_system_shutdown_request() here?


> +    case 'D':
> +        /* Detach packet */
> +        if (!cpu_breakpoint_remove_all(env)) {
> +            gdb_continue(s);
> +            put_packet(s, "OK");
> +            break;
> +        }
>      case 's':
>          if (*p != '\0') {
>              addr = strtoull(p, (char **)&p, 16);
> --- a/exec.c
> +++ b/exec.c
> @@ -1150,6 +1150,20 @@ int cpu_breakpoint_insert(CPUState *env,
>  #endif
>  }
>  
> +/* remove all breakpoints */
> +int cpu_breakpoint_remove_all(CPUState *env) {
> +#if defined(TARGET_HAS_ICE)
> +    int i;
> +    for(i = 0; i < env->nb_breakpoints; i++) {
> +        breakpoint_invalidate(env, env->breakpoints[i]);
> +    }
> +    env->nb_breakpoints = 0;
> +    return 0;
> +#else
> +    return -1;
> +#endif
> +}

Why not just drop the return value and make the 'D' command always succeed?

Best regards
-- 
Edgar E. Iglesias
Axis Communications AB

  reply	other threads:[~2008-05-12 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 13:51 [Qemu-devel] [PATCH] gdbstub improvements for gdb kill/detach/quit Jason Wessel
2008-05-12 11:29 ` Edgar E. Iglesias [this message]
2008-05-13  3:10   ` Jason Wessel

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=20080512112928.GC21455@edgar.se.axis.com \
    --to=edgar.iglesias@axis.com \
    --cc=jason.wessel@windriver.com \
    --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).