From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [patch] Fix arm self-modifying code
Date: Mon, 2 Aug 2004 01:29:58 +0100 [thread overview]
Message-ID: <200408020129.58784.paul@codesourcery.com> (raw)
The patch adds the signal handling necessary to make arm self-modifying code
work. You'll notice it looks remarkably similar to the sparc routine :)
This should fix the "uncaught target signal 11" crash people have been seeing.
Paul
Index: cpu-exec.c
===================================================================
RCS file: /cvsroot/qemu/qemu/cpu-exec.c,v
retrieving revision 1.38
diff -u -p -r1.38 cpu-exec.c
--- cpu-exec.c 14 Jul 2004 17:20:55 -0000 1.38
+++ cpu-exec.c 2 Aug 2004 00:24:46 -0000
@@ -718,6 +719,10 @@ static inline int handle_cpu_signal(unsi
int is_write, sigset_t *old_set,
void *puc)
{
+ /* XXX: locking issue */
+ if (is_write && page_unprotect(address, pc, puc)) {
+ return 1;
+ }
/* XXX: do more */
return 0;
}
next reply other threads:[~2004-08-02 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 0:29 Paul Brook [this message]
2004-08-02 12:21 ` [Qemu-devel] [patch] Fix arm self-modifying code Lennert Buytenhek
2004-08-02 12:38 ` Lennert Buytenhek
2004-08-02 12:39 ` Hetz Ben Hamo
2004-08-02 12:49 ` Lennert Buytenhek
2004-08-02 22:36 ` [Qemu-devel] " Ronald
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=200408020129.58784.paul@codesourcery.com \
--to=paul@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).