All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] X86_64 (AMD64) build segfaults
Date: Thu, 21 Apr 2005 16:11:40 +0100	[thread overview]
Message-ID: <200504211611.40785.paul@codesourcery.com> (raw)
In-Reply-To: <20050421165923.0f4f1185@smirftschs.home.tld>

[Sorry to reply twice, meant to add this onto my last mail]

On Thursday 21 April 2005 15:59, developer@isl-gbr.de wrote:
> Removing the optimizations (the -O2) it does compile, but qemu segfaults
> when trying to start. 

This is normal. qemu is fairly fussy about what optimization options are used 
to compile op.c.

> So what chances do i have ? Sending a report to gcc.gnu.org or what can i
> do to trace this bug down ? I have nearly no idea about assembly, which
> seems to be used in the part its segfaulting.

See http://gcc.gnu.org/bugs.html

Paul

  parent reply	other threads:[~2005-04-21 15:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 14:34 [Qemu-devel] X86_64 (AMD64) build segfaults developer
2005-04-21 14:42 ` Paul Brook
2005-04-21 14:59   ` developer
2005-04-21 15:01     ` Paul Brook
2005-04-21 16:02       ` developer
2005-04-22 14:50       ` developer
2005-04-22 15:01         ` Jonas Maebe
2005-04-22 15:41           ` developer
2005-04-22 16:12             ` Jonas Maebe
2005-04-22 16:30               ` developer
2005-04-22 16:33               ` Paul Brook
2005-04-23  9:05                 ` developer
2005-04-23 11:33                   ` Paul Brook
2006-03-15  8:15                     ` [Qemu-devel] Dynamic compiler future (was Re: X86_64 (AMD64) build segfaults) Antti P Miettinen
2005-04-22 22:12               ` [Qemu-devel] X86_64 (AMD64) build segfaults Joshua Root
2005-04-21 15:11     ` Paul Brook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22 16:35 Jung-uk Kim
2005-04-22 16:49 Jung-uk Kim
2005-04-23  9:06 ` developer
2005-05-02 17:40   ` Jung-uk Kim

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=200504211611.40785.paul@codesourcery.com \
    --to=paul@codesourcery.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 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.