All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel Developers <qemu-devel@nongnu.org>
Cc: Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [TestDays] info mtree abort
Date: Sat, 12 Nov 2011 03:27:55 +0100	[thread overview]
Message-ID: <4EBDD9AB.2070207@suse.de> (raw)
In-Reply-To: <4EBDD460.10103@suse.de>

Am 12.11.2011 03:05, schrieb Andreas Färber:
> On current qemu.git master for qemu-system-x86_64 I observe crashes
> similar to this one when running info mtree on the SDL monitor console:
> 
> *** glibc detected ***
> /home/andreas/QEMU/qemu-rl78/rl78-softmmu/qemu-system-rl78: free():
> invalid pointer: 0x4545454545454545 ***
> 
> #0  0x00007ffff6308d95 in raise () from /lib64/libc.so.6
> #1  0x00007ffff630a2ab in abort () from /lib64/libc.so.6
> #2  0x00007ffff6342ece in __libc_message () from /lib64/libc.so.6
> #3  0x00007ffff6348c06 in malloc_printerr () from /lib64/libc.so.6
> #4  0x00000000004e9024 in mtree_print_mr (mon_printf=0x4ef720
> <monitor_printf>, f=0xf89b10, mr=<optimized out>, level=0, base=0,
> alias_print_queue=0x7fffffffd610)
>     at /home/andreas/QEMU/qemu-rl78/memory.c:1405
> #5  0x00000000004ec8b6 in mtree_info (mon_printf=0x4ef720
> <monitor_printf>, f=0xf89b10) at /home/andreas/QEMU/qemu-rl78/memory.c:1417

Commenting out both g_free()s in QTAILQ_FOREACH_SAFE() in
mtree_print_mr() and mtree_info() respectively avoids this.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2011-11-12  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12  2:05 [Qemu-devel] [TestDays] info mtree abort Andreas Färber
2011-11-12  2:27 ` Andreas Färber [this message]
2011-11-12  7:26 ` Stefan Weil
2011-11-12  9:38   ` Andreas Färber

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=4EBDD9AB.2070207@suse.de \
    --to=afaerber@suse.de \
    --cc=avi@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.