From: David Woodhouse <dwmw2@infradead.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU version 0.5.5
Date: Sun, 09 May 2004 16:53:38 +0100 [thread overview]
Message-ID: <1084118018.4152.3.camel@localhost.localdomain> (raw)
In-Reply-To: <409E0AF2.90507@bellard.org>
On Sun, 2004-05-09 at 12:41 +0200, Fabrice Bellard wrote:
> With the dynamically linked ARM binaries on the QEMU web site, it works,
> so it may be an FPU related bug or a bug in an ARM instruction which was
> not used in the binary I used. It can also be a syscall problem.
>
> The simplest way to debug is to recompile the libc and the dynamic
> linker and to insert "printf" (or write syscalls) at the right place. If
> you have the time and all the needed tools, the bug should be easy to track.
I think I'd prefer to have qemu set LD_DEBUG=all for its child, and
maybe to get its gdb stub working. I'll play...
--
dwmw2
next prev parent reply other threads:[~2004-05-09 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 15:07 [Qemu-devel] QEMU version 0.5.5 Fabrice Bellard
2004-05-08 16:32 ` Hetz Ben Hamo
2004-05-08 18:44 ` Michael Torrie
2004-05-08 21:00 ` [Qemu-devel] " Robert Wittams
2004-05-08 21:12 ` Lennert Buytenhek
2004-05-08 22:14 ` [Qemu-devel] " Jason Gress
2004-05-09 9:38 ` David Woodhouse
2004-05-09 10:41 ` Fabrice Bellard
2004-05-09 13:37 ` Fabrice Bellard
2004-05-09 15:36 ` [Qemu-devel] Slirp not really sending DHCPOFFER? Johannes Schindelin
2004-05-09 15:53 ` David Woodhouse [this message]
2004-05-09 13:43 ` [Qemu-devel] QEMU version 0.5.5 Lennert Buytenhek
-- strict thread matches above, loose matches on Subject: below --
2004-05-08 18:32 Misty De Meo
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=1084118018.4152.3.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.