qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Daniel Gutson <dgutson@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] Fix to 'gdb detach' stub
Date: Tue, 23 Feb 2010 11:30:53 +0100	[thread overview]
Message-ID: <4B83AE5D.8050006@redhat.com> (raw)
In-Reply-To: <4B82F59D.8050204@codesourcery.com>

Am 22.02.2010 22:22, schrieb Daniel Gutson:
> [Re-done with git.]
> With this patch, 'gdb detach' correctly resumes the inferior execution 
> after detaching the debugger.
> The bug was caused by qemu asking gdb to execute a syscall (isatty) 
> after the detach, and then waiting (forever) for the reply. I fixed this 
> by properly setting gdb_syscall_mode appropriately in the 'detach' 
> packet handling, so subsequent syscalls are solved by qemu rather than gdb.
> 
> Signed-off-by: Daniel Gutson <dgutson@codesourcery.com>
> ---
>   gdbstub.c |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/gdbstub.c b/gdbstub.c
> index 91c5f68..92bb36d 100644
> --- a/gdbstub.c
> +++ b/gdbstub.c
> @@ -1848,6 +1848,7 @@ static int gdb_handle_packet(GDBState *s, const 
> char *line_buf)

This line wrap corrupts the patch. Have you tried git send-email?

>       case 'D':
>           /* Detach packet */
>           gdb_breakpoint_remove_all();
> +       gdb_syscall_mode = GDB_SYS_DISABLED;

And indentation is off here (qemu uses four spaces, no tabs).

Kevin

  reply	other threads:[~2010-02-23 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 20:50 [Qemu-devel] [PATCH] Fix to 'gdb detach' stub Daniel Gutson
2010-02-22 21:22 ` [Qemu-devel] " Daniel Gutson
2010-02-23 10:30   ` Kevin Wolf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-26 17:13 [Qemu-devel] " Daniel Gutson
2010-02-26 17:28 ` [Qemu-devel] " Kevin Wolf

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=4B83AE5D.8050006@redhat.com \
    --to=kwolf@redhat.com \
    --cc=dgutson@codesourcery.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).