All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU crash with Fedora Core 2
Date: Thu, 27 May 2004 12:57:47 +0600	[thread overview]
Message-ID: <40B5916B.6000502@ums.usu.ru> (raw)
In-Reply-To: <40B4F861.7000504@bellard.org>

Fabrice Bellard wrote:

> I cannot accept this patch: it breaks qemu-fast with all old libcs. The 
> good solution is to use a specific sigaction call which directly makes 
> the sigaction Linux system call.

What about various #ifdefs or bumping up the requirements?

Also, I could not get qemu-fast working with any glibc >=2.3.1 compiled 
from pristine sources according to instructions from Linux From Scratch.

Qemu-fast compiles, but doesn't work with glibc >=2.3.1. It does not 
compile at all with glibc-2.3.3-cvs with TLS enabled. See my message 
"qemu and modern glibc" for changes to qemu that make qemu-fast at least 
compile on glibc >=2.3.3-cvs. Please confirm privately that you have 
read this message.

The tail of qemu.log is:

----------------
IN:
0x000c625d:  repz stos %ax,%es:(%di)

----------------
IN:
0x000c625d:  repz stos %ax,%es:(%di)

(repeated infinitely without any OUT, even if I add out_asm to the -d 
switch). Plain non-fast qemu works perfectly.

What are known good _pristine_ (not RedHat) glibc versions that are 
capable of producing a good qemu-fast binary?

On what distribution does the qemu development happen? What are 
binutils/gcc/glibc versions?

-- 
Alexander E. Patrakov

      parent reply	other threads:[~2004-05-28 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 22:47 [Qemu-devel] QEMU crash with Fedora Core 2 Hetz Ben Hamo
2004-05-26  9:00 ` David Woodhouse
2004-05-26 14:24   ` Hetz Ben Hamo
2004-05-26 20:04   ` Fabrice Bellard
2004-05-27  6:36     ` Hetz Ben Hamo
2004-05-27  6:57     ` Alexander E. Patrakov [this message]

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=40B5916B.6000502@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --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.