From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] gdbstub.c fix for SIGINT
Date: Thu, 20 Apr 2006 01:16:20 +0700 [thread overview]
Message-ID: <200604200116.20700.a_mulyadi@softhome.net> (raw)
In-Reply-To: <44439421.9060100@windriver.com>
Hi...
> Attached is a patch to add the case for interrupting the gdbstub and
> sending the correct signal to gdb.
Excellent. I haven't tested by myself, but could you test your patch
together with Andre Pech's patch that I put in
http://qemu.dad-answers.com/viewtopic.php?p=2809#2809?
BTW, Paul brook also put a patch related with breakpoint TLB
invalidation in
http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/exec.c.diff?tr1=1.74&tr2=1.75&r1=text&r2=text
(from Paul Brook's posting at qemu-devel on April 9th 2006 )
I think it would be great if these patch combo can finally squashed the
gdbstub bug related to missed breakpoints once and for all.
regards
Mulyadi
prev parent reply other threads:[~2006-04-19 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 6:27 [Qemu-devel] Solaris Linux x86 binary compatibility Peter Firmstone
2006-04-17 13:12 ` [Qemu-devel] [PATCH] gdbstub.c fix for SIGINT Jason Wessel
2006-04-19 18:16 ` Mulyadi Santosa [this message]
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=200604200116.20700.a_mulyadi@softhome.net \
--to=a_mulyadi@softhome.net \
--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).