All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Adam Lackorzynski <adam@os.inf.tu-dresden.de>,
	Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [BUG 1.2] qemu-system-arm segfault
Date: Wed, 29 Aug 2012 07:19:53 +0200	[thread overview]
Message-ID: <503DA679.9030503@weilnetz.de> (raw)
In-Reply-To: <20120828202608.GB6424@os.inf.tu-dresden.de>

Am 28.08.2012 22:26, schrieb Adam Lackorzynski:
> Hi,
>
> I'm getting a segfault for qemu-system-arm (git).
> Git bisect points to 33e95c6328a3149a52615176617997c4f8f7088b.
> Host is x86-32, I'm not getting it in a 64bit environment.
> However, valgrind is showing a similar output for arm_gic_class_init and
> arm_gic_init.
>
>

Hi,

my quick test on 32 bit Ubuntu Lucid confirms this segfault.
Valgrind does not work in this environment.

Anthony, I think this might be important for QEMU 1.2.

Regards,

Stefan W.

  reply	other threads:[~2012-08-29  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 20:26 [Qemu-devel] qemu-system-arm segfault Adam Lackorzynski
2012-08-29  5:19 ` Stefan Weil [this message]
2012-08-29  7:44   ` [Qemu-devel] [BUG 1.2] " Peter Maydell

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=503DA679.9030503@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=adam@os.inf.tu-dresden.de \
    --cc=aliguori@us.ibm.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.