From: Dirk Behme <dirk.behme@googlemail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] MIPS little endian user space emulation
Date: Sat, 09 Sep 2006 09:16:33 +0200 [thread overview]
Message-ID: <45026A51.2080501@gmail.com> (raw)
In-Reply-To: <200609100013.42650.hoan@wanadoo.fr>
wangji wrote:
>>Seems to me that it gets a wrong jump address via gp in t9:
>>
>>0x401fa00c: lw t9,-32600(gp)
>>...
>>0x401fa01c: jalr t9
...
> yes,I got similar error,but if I "static" compile then everything looks ok !
Thanks for the hint! static works for me as well.
So, maybe a toolchain (glibc?) issue?
> qemu-0.82 ,crosstool-0.38 from my latest livecdToolkit
> http://mirror.opf.slu.cz/scratchbox/iso/ScratchboxMultiCpu-2.3.iso
I use qemu-snapshot-2006-09-07_23 and toolchain created with
crosstool-0.42 configuration
cat mipsel.dat gcc-3.4.1-glibc-2.3.2.dat
Regards
Dirk
Btw: Do you can connect and then step/continue with gdb to
qemu-mipsel?
next prev parent reply other threads:[~2006-09-09 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 16:35 [Qemu-devel] MIPS little endian user space emulation Dirk Behme
2006-09-08 20:33 ` Stefan Weil
2006-09-09 7:41 ` Dirk Behme
2006-09-09 18:00 ` Stefan Weil
2006-09-10 10:24 ` wangji
2006-09-09 22:13 ` wangji
2006-09-09 7:16 ` Dirk Behme [this message]
2006-09-10 2:34 ` wangji
2006-09-10 8:49 ` wangji
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=45026A51.2080501@gmail.com \
--to=dirk.behme@googlemail.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).