qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [patch] Arm syscall bug
Date: Sat, 23 Apr 2005 16:31:09 +0100	[thread overview]
Message-ID: <200504231631.10630.paul@codesourcery.com> (raw)

The arm-user syscall emulation always passes zero for the 6th syscall 
argument. This breaks the mmap2 syscall, and possibly others.

Patch below fixes this.

Paul

Index: linux-user/main.c
===================================================================
RCS file: /cvsroot/qemu/qemu/linux-user/main.c,v
retrieving revision 1.63
diff -u -p -r1.63 main.c
--- linux-user/main.c	17 Apr 2005 19:16:13 -0000	1.63
+++ linux-user/main.c	23 Apr 2005 15:25:32 -0000
@@ -373,7 +376,7 @@ void cpu_loop(CPUARMState *env)
                                               env->regs[2],
                                               env->regs[3],
                                               env->regs[4],
-                                              0);
+                                              env->regs[5]);
                 } else {
                     goto error;
                 }

                 reply	other threads:[~2005-04-23 15:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200504231631.10630.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).