From: Herbert Poetzl <herbert@13thfloor.at>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problem with PPC user emulation.
Date: Fri, 14 May 2004 22:33:28 +0200 [thread overview]
Message-ID: <20040514203327.GC8774@MAIL.13thfloor.at> (raw)
In-Reply-To: <Pine.LNX.4.43.0405142143010.28976-100000@thinkpad.gardas.net>
On Fri, May 14, 2004 at 09:44:19PM +0200, Karel Gardas wrote:
> On Fri, 14 May 2004, Jocelyn Mayer wrote:
>
> > On Fri, 2004-05-14 at 21:26, Karel Gardas wrote:
> > > On Fri, 14 May 2004, Jocelyn Mayer wrote:
> > >
> > > > On Fri, 2004-05-14 at 19:59, Karel Gardas wrote:
> > > > > Hello,
> > > > >
> > > > > I've tried PPC user emulation provided by this week source tree, but w/o
> > > > > success. I've tested crosstool's 4 test binaries (hello world in c/c++
> > > > > static and dynamic) but all four crash with:
> > > > >
> > > > > thinkpad:/mnt/karel/cross-gcc/result/powerpc-405-linux-gnu/gcc-3.4.0-glibc-2.3.2/tmp$ ppc.sh ./powerpc-405-linux-gnu-hello
> > > > > *** ERROR: idx a0 already assigned to a direct opcode
> > > > > *** ERROR: unable to join indirect table idx [a0-37]
> > > > > *** ERROR initializing PPC instruction 0xa0 0x37 0xfe
> > > > > /opt/qemu-scripts/bin/ppc.sh: line 3: 3496 Segmentation fault qemu-ppc -L /mnt/karel/cross-gcc/result/powerpc-405-linux-gnu/gcc-3.4.0-glibc-2.3.2/powerpc-405-linux-gnu/ $@
> > > > > thinkpad:/mnt/karel/cross-gcc/result/powerpc-405-linux-gnu/gcc-3.4.0-glibc-2.3.2/tmp$
> > > > >
> > > > > I used crosstool-0.28-pre13 for building ppc crosscompiler which is
> > > > > gcc3.4.0 and glibc2.3.2 combination.
> > > > >
> > > >
> > > > What is your host machine ?
> > >
> > > Debian GNU/Linux 3.0.
> >
> > On a PC ?
>
> Err, sorry, yes, x86.
>
> > > Sure! I will send you the smaller one (C statically linked hello world
> > > app)
> >
> > Well, I need the Qemu executable, not the emulated program, because the
> > point you report is a bug inside qemu: it stops before trying to execute
> > any emulated code, and I want to study the way it's been compiled by
> > gcc...
>
> Ah, yes, sorry, I have not understood this. I will send it to you
> immediately. FYI: Qemu was compiled by gcc3.4.0 + fsf binutils 2.14
hmm, IIRC I had some issues with binutils 2.14 and gcc 3.4 ..
I upgraded to binutils 2.15.90.0.3 which fixed that ...
(might be completely unrelated, so do not rely on that)
best,
Herbert
> Thanks,
>
> Karel
> --
> Karel Gardas kgardas@objectsecurity.com
> ObjectSecurity Ltd. http://www.objectsecurity.com
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-05-14 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 17:59 [Qemu-devel] Problem with PPC user emulation Karel Gardas
2004-05-14 19:25 ` Jocelyn Mayer
2004-05-14 19:26 ` Karel Gardas
2004-05-14 19:42 ` Jocelyn Mayer
2004-05-14 19:44 ` Karel Gardas
2004-05-14 20:33 ` Herbert Poetzl [this message]
2004-05-14 20:42 ` Karel Gardas
2004-05-14 21:44 ` J. Mayer
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=20040514203327.GC8774@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=kgardas@objectsecurity.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).