Hi list, let me start stating the obvious: valgrind is awesome and has helped me to spot quite a few nasty things in my code - thank you for your commitment in creating and improving this incredibly helpful tool!
I have just updated to valgrind 3.4.1 compiled from source to find some odd behaviour of my program (which now turned out to be a libc bug). Anyway, the matter at hand really is that valgrind trashes my console with strange characters, some of them proper ascii ones, some of them non-printable or control characters. 3.3.1 did not do this, but otherwise produced pretty much the same output. I'll gladly give you a taste (though I highly doubt it will be rendered correctly for you) There you go: --941206317-Æ Memcheck, a memory error detector --941206317-Æ Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al. --941206317-Æ Using LibVEX rev 1884, a library for dynamic binary translation. --941206317-Æ Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP. --941206317-Æ Using valgrind-3.4.1, a dynamic binary instrumentation framework. --941206317-Æ Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al. --941206317-Æ For more details, rerun with: -v --941206317-Æ (each ..17- is followed by a Danish(?) AE-character) [...] 240000000( Warning: set address range perms: large range [0x8bd2028, 0x170b3c28) (defined) (the 240... is bracketed by something that is rendered as the outline of a square in bash) [...] Ì1652879052h Invalid free() / delete / delete[] Z67227738 at 0x401D05A: free (vg_replace_malloc.c:323) œ69949373 by 0x42B57BD: (within /lib/tls/i686/cmov/libc-2.3.6.so) q69947249 by 0x42B4F71: (within /lib/tls/i686/cmov/libc-2.3.6.so) 67212574 by 0x401951E: _vgnU_freeres (vg_preloaded.c:60) 69434883 by 0x4237E03: _Exit (in /lib/tls/i686/cmov/libc-2.3.6.so) ¯68939439 by 0x41BEEAF: (below main) (in /lib/tls/i686/cmov/libc-2.3.6.so) -1640719376-õ Address 0x4184550 is not stack'd, malloc'd or (recently) free'd 1 1 ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 21 from 1) 0 malloc/free: in use at exit: 0 bytes in 0 blocks. 0 malloc/free: 11,744 allocs, 11,745 frees, 360,837,120 bytes allocated. 1 For counts of detected errors, rerun with: -v 1 All heap blocks were freed -- no leaks are possible. Ok, this even renders absurdly in Thunderbird, but I hope you get the gist. Repeated runs of valgrind produce the same weird characters, i.e. it is deterministic instead of random stuff. Since this behaviour starts right from the beginning, I conclude that it is not (at least entirely) due to potential memory corruption by my code - right? I'm running this in GNU bash, version 3.1.17(1)-release (i486-pc-linux-gnu) on a Debian 4 like this Linux 2.6.18-6-k7 #1 SMP Tue May 5 01:21:08 UTC 2009 i686 GNU/Linux and compiled everything with gcc/gfortran 4.3.3 Anything else I should provide? I'd be happy for any pointers! Cheers, Dennis -- Zentrum für Technomathematik, AG Optimierung und Optimale Steuerung fon: 0421-218.63866 fax: 0421-218.9863866 web: www.worhp.de
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
