All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PULL] Memory core space reduction
Date: Tue, 28 Feb 2012 12:31:20 -0600	[thread overview]
Message-ID: <4F4D1D78.6050304@codemonkey.ws> (raw)
In-Reply-To: <4F4D19C5.8030507@redhat.com>

On 02/28/2012 12:15 PM, Avi Kivity wrote:
> On 02/28/2012 08:13 PM, Anthony Liguori wrote:
>>
>> FWIW, I'm processing this PULL request right now and I'm seeing a SEGV
>> too.  The backtrace is a malloc failure in QOM.
>>
>
> How do we reproduce this?

It looks like just repeatedly running QEMU with a -device option does it.

It's only about 10% reproducible for me.  I'm thinking it's a heap corruption.

Regards,

Anthony Liguori

>

  reply	other threads:[~2012-02-28 18:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 12:25 [Qemu-devel] [PULL] Memory core space reduction Avi Kivity
2012-02-28 12:26 ` Avi Kivity
2012-02-28 17:59 ` Michael S. Tsirkin
2012-02-28 18:13   ` Anthony Liguori
2012-02-28 18:15     ` Avi Kivity
2012-02-28 18:31       ` Anthony Liguori [this message]
2012-02-28 18:56       ` Anthony Liguori
2012-02-28 19:14       ` Anthony Liguori
2012-02-28 19:17         ` Avi Kivity
2012-02-28 19:20           ` Anthony Liguori
2012-02-28 22:58             ` Michael S. Tsirkin
2012-02-29 10:09               ` Avi Kivity
2012-02-29 10:23                 ` Michael S. Tsirkin
2012-02-29 10:53                   ` Avi Kivity
2012-02-29 11:25                     ` Michael S. Tsirkin
2012-02-29 11:31                       ` Avi Kivity
2012-02-29 11:45                         ` Avi Kivity
2012-02-29 14:15                           ` Michael S. Tsirkin
2012-02-29 11:27                     ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2012-02-28 12:24 Avi Kivity

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=4F4D1D78.6050304@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=mst@redhat.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.