All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gutson <dgutson@codesourcery.com>
To: qemu-devel@nongnu.org, kwolf@redhat.com, daniel.gutson@gmail.com
Subject: [Qemu-devel] Re: Re: [PATCH] Fix to 'gdb detach' stub
Date: Fri, 26 Feb 2010 14:13:50 -0300	[thread overview]
Message-ID: <4B88014E.5040806@codesourcery.com> (raw)

Hello Kevin,
	please let me know if this works.
If so, please remember that I'd need somebody to commit this for me, since I don't have write-access.

Undoing line wrap and tabs.

Thanks!
	Daniel.

[old same text.]
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)
     case 'D':
         /* Detach packet */
         gdb_breakpoint_remove_all();
+        gdb_syscall_mode = GDB_SYS_DISABLED;
         gdb_continue(s);
         put_packet(s, "OK");
         break;
-- 
1.6.2.4

             reply	other threads:[~2010-02-26 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 17:13 Daniel Gutson [this message]
2010-02-26 17:28 ` [Qemu-devel] Re: [PATCH] Fix to 'gdb detach' stub Kevin Wolf
2010-02-27 15:22 ` [Qemu-devel] " Aurelien Jarno

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=4B88014E.5040806@codesourcery.com \
    --to=dgutson@codesourcery.com \
    --cc=daniel.gutson@gmail.com \
    --cc=kwolf@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.