From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 786440 <786440@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 786440] [NEW] qcow2 double free
Date: Mon, 23 May 2011 10:46:04 +0100 [thread overview]
Message-ID: <BANLkTinQuAz+bUY21Dv487ccFKW-2xd=mw@mail.gmail.com> (raw)
In-Reply-To: <20110522075851.3340.21746.malonedeb@soybean.canonical.com>
On Sun, May 22, 2011 at 8:58 AM, Andrew Kroll <786440@bugs.launchpad.net> wrote:
> Public bug reported:
>
> version 0.14.1 when using qcow2 images, after some time, glibc detects a
> double free or corruption.
Any specific information on what the guest was doing? Was it doing
heavy I/O or was it idle?
Are you using IDE emulation or virtio-blk?
Please provide a backtrace:
1. Build with ./configure --disable-strip (or use matching -debuginfo
packages from your distro)
2. Run with gdb --args path/to/qemu [...args...]
When the abort happens please use the "bt" GDB command to display a backtrace.
Stefan
next prev parent reply other threads:[~2011-05-23 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 7:58 [Qemu-devel] [Bug 786440] [NEW] qcow2 double free Andrew Kroll
2011-05-23 9:46 ` Stefan Hajnoczi [this message]
2016-10-18 21:15 ` [Qemu-devel] [Bug 786440] " T. Huth
2016-12-18 4:17 ` Launchpad Bug Tracker
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='BANLkTinQuAz+bUY21Dv487ccFKW-2xd=mw@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=786440@bugs.launchpad.net \
--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).