From: Thiemo Seufer <ths@networkno.de>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: QEMU MIPS user space emulation issue
Date: Mon, 11 Sep 2006 22:30:08 +0100 [thread overview]
Message-ID: <20060911213008.GD13414@networkno.de> (raw)
In-Reply-To: <450589A6.5040808@gmail.com>
Dirk Behme wrote:
> Hi,
>
> we have an issue using QEMUs MIPS user space emulation
> running programs compiled with mipsel glibc based
> crosscompiler [1]. Because I'm not sure if it's a QEMU or
> toolchain (or anything else?) issue, I'd like to ask the
> experts here.
>
> Up to now, the conclusion from [1] is that QEMUs mipsel user
> space emulation fails executing a simple hello world program
> if compiled with glibc based mipsel toolchain build with
> crosstool and linked dynamically. Compiled with toolchain
> using uClib or same program linked statically (-static) is okay.
So this is unlikely to be a kernel problem.
> For example, hello world compiled with mipsel toolchain
> build with crosstool-0.42 configuration
>
> cat mipsel.dat gcc-3.4.1-glibc-2.3.2.dat
>
> fails if dynamically linked. As mentioned above, using
> -static is okay.
Start from a known working mipsel userland, e.g. the one from Debian
unstable, and use it to isolate the bug.
> If failing, debug output shows that code
>
> ...
> 0x401fa00c: lw t9,-32600(gp)
> 0x401fa010: addiu a0,a0,30820
> 0x401fa014: addiu a1,a1,29452
> 0x401fa018: addiu a3,a3,25856
> 0x401fa01c: jalr t9
> 0x401fa020: li a2,161
> ...
Sa a guess, it might be a dynamic symbol mis-resolved by the ld.so.
Thiemo
prev parent reply other threads:[~2006-09-11 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 16:07 QEMU MIPS user space emulation issue Dirk Behme
2006-09-11 21:30 ` Thiemo Seufer [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=20060911213008.GD13414@networkno.de \
--to=ths@networkno.de \
--cc=dirk.behme@googlemail.com \
--cc=linux-mips@linux-mips.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