qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Rene Horn" <the.rhorn@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] glibc abort if -snapshot is used
Date: Tue, 22 Aug 2006 22:40:47 -0500	[thread overview]
Message-ID: <b8e8c9290608222040y6fa1409al132923c331c8fab7@mail.gmail.com> (raw)
In-Reply-To: <1156291360.28673.8.camel@r51.oakcourt.dyndns.org>

[-- Attachment #1: Type: text/plain, Size: 2389 bytes --]

Why not just build it right from the source instead of using debhelper?
With that, just have install into /usr/local.

Rene

On 8/22/06, Andrew Barr <andrew.james.barr@gmail.com> wrote:
>
> Hi,
>
> I am installing some software (iTunes) in my Windows 2000 SP4 virtual
> machine. I don't know what it is going to /do/, specifically, to my VM
> so I would like to run QEMU in snapshot mode so that I can commit system
> changes only if desired. However, when I run qemu like this, I get into
> trouble:
>
> andrew@r51:~$ qemu -hda .disk/win2k.dsk -m 256 -snapshot -kernel-kqemu
> -usb -usbdevice tablet -localtime -smb /home/andrew
> *** glibc detected *** double free or corruption (fasttop): 0xAborted
>
> Sometimes it finishes printing the address: 0x09b2c738
>
> The SDL window never comes up, the abort is instanenous. I did a
> backtrace but because I built Debian packages debhelper strips the debug
> information out, so it doesn't say much. I can rebuild QEMU with debug
> information and obtain a proper backtrace if it would be useful to
> someone.
>
> This is a QEMU 0.8.2 CVS snapshot of 2006/08/19. I did a 'cvs up' on my
> source tree, only the documentation has been updated since then.
> Normally I run this VM exactly the same except without the '-snapshot'
> parameter. If I remove that, it starts up as expected.
>
> The disk image is QCOW2 and kqemu is 1.3.0pre9 (BTW, '-no-kqemu' without
> '-kernel-kqemu' makes no difference)
>
> glibc is 2.3.6-ds1-2 from Debian sid. QEMU was compiled with GCC 3.4.6
> also from Debian.
>
> --
> Andrew Barr | http://www.oakcourt.dyndns.org/~andrew/
>
> All parts should go together without forcing. You must remember that
> the parts you are reassembling were disassembled by you. Therefore, if
> you can't get them together again, there must be a reason. By all
> means, do not use a hammer.
>   -- IBM maintenance manual (1925)
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>



-- 
the.rhorn@gmail.com, rhorn@sdf.lonestar.org,
hornr18@uwosh.edu (UW-Oshkosh email address),
http://rhorn.unixcab.org - a bunch of experimental stuff
SDF Public Access UNIX System - http://sdf.lonestar.org

Jay Leno in response to Colin Powell's deadline for an Iraqi
constitution:
"They can take ours.  After all, we aren't using it..."

[-- Attachment #2: Type: text/html, Size: 3183 bytes --]

  reply	other threads:[~2006-08-23  3:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  0:02 [Qemu-devel] glibc abort if -snapshot is used Andrew Barr
2006-08-23  3:40 ` Rene Horn [this message]
2006-08-23 16:14   ` Andrew Barr
2006-08-23 16:48     ` Leonardo E. Reiter
2006-08-23 21:55 ` Stefan Weil
2006-08-23 22:00   ` Stefan Weil

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=b8e8c9290608222040y6fa1409al132923c331c8fab7@mail.gmail.com \
    --to=the.rhorn@gmail.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 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).