From: Riku Voipio <riku.voipio@iki.fi>
To: Kai Backman <kaib@google.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: problems with mmap on qemu-arm
Date: Thu, 18 Jun 2009 21:55:52 +0300 [thread overview]
Message-ID: <20090618185551.GB24046@kos.to> (raw)
In-Reply-To: <c7187c3d0906171338t1a66b32ai73e7acd615ecbf@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1876 bytes --]
On Wed, Jun 17, 2009 at 11:38:32PM +0300, Kai Backman wrote:
> I tracked this down to the code in linux-user/syscall.c. The mmap code
> seems broken, it assumes arg1 is a pointer to an array where the real
> arguments are. Given arg1 = 0 the memory access check fails.
> The code I'm working on will happily take mmap2 instead so I have a
> workaround. Does someone have an opinion on the state of the mmap code?
> Kai
looking at old_mmap() for arm in kernel, qemu seems to the right thing. Ie
you are probably calling mmap the wrong way, you are supposed to give it a
array.
mmap syscall is depreceated, glibc uses mmap2 since forever.
> On Wed, Jun 17, 2009 at 8:54 PM, Kai Backman <[1]kaib@google.com> wrote:
>
> I'm running qemu-arm and see the following output from mmap with 'strace
> qemu-arm -strace' (for both host and traget strace output):
> mmap(NULL, 32800, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x2ad329b46000
> 4023 mmap(0,131072,7,34,-1,0) = 0xfffffff2
> When my program later tries to read memory at 0xfffffffe it fails with a
> SIGSEGV:
> Program received signal SIGSEGV, Segmentation fault.
> 1: x/i $pc 0xce30: ldr r1, [r5]
> (gdb) i r
> r5 0xfffffffe -2
> Why does qemu-arm return such high addresses on a 32 bit platform and
> why is the memory inaccessible? If this doesn't seem like an obvious bug
> in my code, where in the qemu code should I start looking for how mmap
> works?
> Kai
> --
> Kai Backman, Software Engineer, [2]kaib@google.com
>
> --
> Kai Backman, Software Engineer, [3]kaib@google.com
>
> References
>
> Visible links
> 1. mailto:kaib@google.com
> 2. mailto:kaib@google.com
> 3. mailto:kaib@google.com
prev parent reply other threads:[~2009-06-18 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 17:54 [Qemu-devel] problems with mmap on qemu-arm Kai Backman
2009-06-17 20:38 ` [Qemu-devel] " Kai Backman
2009-06-18 18:55 ` Riku Voipio [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=20090618185551.GB24046@kos.to \
--to=riku.voipio@iki.fi \
--cc=kaib@google.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).