From: Sylvain Petreolle <spetreolle@yahoo.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] valgrind functionality in qemu?
Date: Mon, 22 Nov 2004 17:30:21 +0100 (CET) [thread overview]
Message-ID: <20041122163021.8747.qmail@web26809.mail.ukl.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0411221255210.5151@wgmdd8.biozentrum.uni-wuerzburg.de>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
Talking about qemu and valgrind,
qemu immediately exits if you run it under valgrind.
I tried it with latest qemu CVS and valgrind 2.2.0.
Actual cmdline was :
valgrind --tool=memcheck --leak-check=yes qemu -boot d -cdrom /home/syl/qemu_images/tccboot.iso
(I attached the result)
> On Sat, 20 Nov 2004, Marc E. Fiuczynski wrote:
>
> > Just curious whether anyone has thought about putting things like the
> > memory profiling, thread debugging, etc. features of valgrind
> > (http://valgrind.kde.org/) into qemu?!
>
=====
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
humans are like computers,
yesterday the BIOS was all
- today its just a word
[-- Attachment #2: qemuresult --]
[-- Type: application/octet-stream, Size: 2218 bytes --]
==3247== Memcheck, a memory error detector for x86-linux.
==3247== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward et al.
==3247== Using valgrind-2.2.0, a program supervision framework for x86-linux.
==3247== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al.
==3247== For more details, rerun with: -v
==3247==
==3247== Warning: set address range perms: large range 138739712, a 0, v 1
==3247== Syscall param write(buf) contains uninitialised or unaddressable byte(s)
==3247== at 0x1BAB6723: __write_nocancel (in /lib/tls/libc-2.3.3.so)
==3247== by 0x1BC2E12F: (within /usr/X11R6/lib/libX11.so.6.2)
==3247== by 0x1BC2EECE: _X11TransWrite (in /usr/X11R6/lib/libX11.so.6.2)
==3247== by 0x1BC0E721: (within /usr/X11R6/lib/libX11.so.6.2)
==3247== Address 0x1BCCC30E is 14 bytes inside a block of size 16384 alloc'd
==3247== at 0x1B9053FD: calloc (vg_replace_malloc.c:176)
==3247== by 0x1BC0055D: XOpenDisplay (in /usr/X11R6/lib/libX11.so.6.2)
==3247== by 0x1B994913: (within /usr/lib/libSDL-1.2.so.0.7.0)
==3247== by 0x1B989E03: SDL_VideoInit (in /usr/lib/libSDL-1.2.so.0.7.0)
==3247==
==3247== ERROR SUMMARY: 3 errors from 1 contexts (suppressed: 39 from 1)
==3247== malloc/free: in use at exit: 139106106 bytes in 354 blocks.
==3247== malloc/free: 1407 allocs, 1053 frees, 139234616 bytes allocated.
==3247== For counts of detected errors, rerun with: -v
==3247== searching for pointers to 354 not-freed blocks.
==3247== checked 19790712 bytes.
==3247==
==3247==
==3247== 8 bytes in 1 blocks are definitely lost in loss record 1 of 29
==3247== at 0x1B9054EA: realloc (vg_replace_malloc.c:197)
==3247== by 0x1BC50FF2: (within /usr/X11R6/lib/libX11.so.6.2)
==3247== by 0x1BC5260E: (within /usr/X11R6/lib/libX11.so.6.2)
==3247== by 0x1BC5341B: (within /usr/X11R6/lib/libX11.so.6.2)
==3247==
==3247== LEAK SUMMARY:
==3247== definitely lost: 8 bytes in 1 blocks.
==3247== possibly lost: 0 bytes in 0 blocks.
==3247== still reachable: 139105898 bytes in 352 blocks.
==3247== suppressed: 200 bytes in 1 blocks.
==3247== Reachable blocks (those to which a pointer was found) are not shown.
==3247== To see them, rerun with: --show-reachable=yes
next prev parent reply other threads:[~2004-11-22 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 21:34 [Qemu-devel] Downloaded files are corrupt Aaron McDonald
2004-11-18 21:45 ` Magnus Damm
2004-11-18 22:28 ` [Qemu-devel] " Ronald
2004-11-18 23:09 ` Ronald
2004-11-21 3:20 ` [Qemu-devel] " Julian Seward
2004-11-21 3:32 ` [Qemu-devel] valgrind functionality in qemu? Marc E. Fiuczynski
2004-11-22 12:05 ` Johannes Schindelin
2004-11-22 16:30 ` Sylvain Petreolle [this message]
2004-11-22 18:14 ` [Qemu-devel] " Ben Pfaff
2004-11-22 18:50 ` Johannes Schindelin
2004-11-22 19:17 ` Ben Pfaff
2004-11-21 16:46 ` [Qemu-devel] Downloaded files are corrupt Martin Jansa
2004-11-21 18:30 ` Julian Seward
2004-11-21 18:41 ` [Qemu-devel] " Ronald
2004-11-21 19:59 ` [Qemu-devel] " Fabrice Bellard
2004-11-21 20:32 ` Martin Jansa
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 15:45 [Qemu-devel] valgrind functionality in qemu? Blue Swirl
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=20041122163021.8747.qmail@web26809.mail.ukl.yahoo.com \
--to=spetreolle@yahoo.fr \
--cc=qemu-devel@nongnu.org \
--cc=spetreolle@users.sourceforge.net \
/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).