qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Meador Inge <meadori@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH v2 0/1] Fix GDB semihosting
Date: Fri, 17 Feb 2012 10:21:20 -0600	[thread overview]
Message-ID: <1329495681-5187-1-git-send-email-meadori@codesourcery.com> (raw)

Hi All,

GDB semihosting support is broken in the current trunk.  When debugging a
basic "Hello, World" application via the QEMU GDB stub:

   $ qemu-system-arm -s -S -M integratorcp -cpu any --semihosting
     --monitor null --serial null -kernel hello

GDB (7.2.50) receives an interrupt before anything is printed:

   Program received signal SIGINT, Interrupt.

The fundamental issue is that the GDB server implementation sends syscall
requests while the system CPU is still running and isn't prepared to handle
the replies.  This patch fixes the problem by delaying syscall request until
the system CPU has stopped.

* Changes from v1
 - At the suggestion of Peter Maydell I changed the implementation to delay
   sending syscall requests until the CPU has stopped instead of incorrectly
   attempting to just suppress the sending of 'T' status replies.

Meador Inge (1):
  gdbserver: Don't send a GDB syscall until the system CPU is stopped

 gdbstub.c |   44 ++++++++++++++++++++++++++++----------------
 1 files changed, 28 insertions(+), 16 deletions(-)

-- 
1.7.7.6

             reply	other threads:[~2012-02-17 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17 16:21 Meador Inge [this message]
2012-02-17 16:21 ` [Qemu-devel] [PATCH v2 1/1] gdbserver: Don't send a GDB syscall until the system CPU is stopped Meador Inge
2012-02-20 16:18   ` Peter Maydell
2012-03-06 19:05     ` Peter Maydell

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=1329495681-5187-1-git-send-email-meadori@codesourcery.com \
    --to=meadori@codesourcery.com \
    --cc=peter.maydell@linaro.org \
    --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).