From: fabrice.bellard@free.fr
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] cvs compiles but doesn't work
Date: Sat, 31 May 2003 12:15:40 +0200 (CEST) [thread overview]
Message-ID: <1054376140.3ed880ccdd8cc@imp.free.fr> (raw)
In-Reply-To: <20030530073911.GF845@suse.de>
Hi,
I tested qemu compiled with gcc 2.95.3 on PowerPC and it passes the regression
test. I think it is a glibc or compiler problem. Which version of gcc and glibc
do you use ?
Fabrice.
Quoting Jens Axboe <qemu@kernel.dk>:
> Hi,
>
> With the #endif and data/sdata change, it compiles here again but
> still
> doesn't work. qemu appears to spin forever, gdb shows:
>
> axboe@apu:/home/axboe/qemu-cvs $ gdb ./qemu
> GNU gdb 5.3-debian
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and
> you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "powerpc-linux"...
> (gdb) r /usr/gnemul/qemu-i386/bin/test-i386
> Starting program: /home/axboe/qemu-cvs/qemu
> /usr/gnemul/qemu-i386/bin/test-i386
>
> Program received signal SIGINT, Interrupt.
> 0x60331614 in code_gen_buffer ()
> (gdb) bt
> #0 0x60331614 in code_gen_buffer ()
> #1 0x6002629c in cpu_x86_exec (env1=0x60191528) at exec-i386.c:261
> #2 0x60004928 in cpu_loop (env=0x0) at main.c:139
> #3 0x60005064 in main (argc=134512880, argv=0x7ffffd44) at main.c:423
> #4 0x5fe2906c in __libc_start_main () from /lib/libc.so.6
> #5 0x5fe28efc in __libc_start_main () from /lib/libc.so.6
>
> Attached is the log file, host is ppc.
>
> --
> Jens Axboe
>
>
next prev parent reply other threads:[~2003-05-31 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 7:39 [Qemu-devel] cvs compiles but doesn't work Jens Axboe
2003-05-31 10:15 ` fabrice.bellard [this message]
2003-06-03 9:15 ` Jens Axboe
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=1054376140.3ed880ccdd8cc@imp.free.fr \
--to=fabrice.bellard@free.fr \
--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).