From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu segfault
Date: Thu, 20 May 2004 16:09:01 +0200 [thread overview]
Message-ID: <40ACBBFD.50705@bellard.org> (raw)
In-Reply-To: <40AC966D.1030800@ums.usu.ru>
Alexander E. Patrakov wrote:
> To reproduce the segfault:
>
> Downolad the image of RedHat 7.0 boot floppy:
>
> http://ftp.redhat.com/pub/redhat/linux/7.0/en/os/i386/images/boot.img
>
> Execute qemu with the following command line:
>
> /usr/local/bin/qemu -fda boot.img -m 32 -boot a
>
> Then press Enter in the boot loader screen. qemu will segfault. The
> segfault does not happen with qemu-fast.
>
> Any response will be appreciated, a fix will be appreciated even more.
> The best is if you fix it and create a small testcase for regression tests.
It is fixed in the CVS version.
Fabrice.
next prev parent reply other threads:[~2004-05-20 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 11:28 [Qemu-devel] qemu segfault Alexander E. Patrakov
2004-05-20 14:09 ` Fabrice Bellard [this message]
2004-05-20 16:00 ` David Sibai
2004-05-20 19:55 ` vaise
2004-05-21 2:20 ` Alexander E. Patrakov
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=40ACBBFD.50705@bellard.org \
--to=fabrice@bellard.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 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).