Dan Kegel schrieb: > On Thu, Jun 4, 2009 at 6:16 AM, Dennis Wassel > <[email protected]> wrote: >> 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. > > What happens if you use --log-file=foo.log? Does the garbage go in the log > file instead of the console?
$ valgrind --log-file=foo.log /bin/true $ cat foo.log --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-Æ Ù-3289-Æ My PID = 26317, parent PID = 3289. Prog and args are: Ù-3289-Æ /bin/true -0-Æ 1 1 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 11 from 1) 0 malloc/free: in use at exit: 0 bytes in 0 blocks. 0 malloc/free: 2 allocs, 2 frees, 36 bytes allocated. 1 For counts of detected errors, rerun with: -v 1 All heap blocks were freed -- no leaks are possible. Yep, it does. > What if you valgrind /bin/true? Still garbage? $ valgrind /bin/true --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-Æ 1 1 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 11 from 1) 0 malloc/free: in use at exit: 0 bytes in 0 blocks. 0 malloc/free: 2 allocs, 2 frees, 36 bytes allocated. 1 For counts of detected errors, rerun with: -v 1 All heap blocks were freed -- no leaks are possible. Still garbage. > What if you switch back to 3.3.1? $ valgrind /bin/true ==27327== Memcheck, a memory error detector. ==27327== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==27327== Using LibVEX rev 1854, a library for dynamic binary translation. ==27327== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==27327== Using valgrind-3.3.1, a dynamic binary instrumentation framework. ==27327== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==27327== For more details, rerun with: -v ==27327== ==27327== ==27327== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 11 from 1) ==27327== malloc/free: in use at exit: 0 bytes in 0 blocks. ==27327== malloc/free: 2 allocs, 2 frees, 36 bytes allocated. ==27327== For counts of detected errors, rerun with: -v ==27327== All heap blocks were freed -- no leaks are possible. No garbage! Thanks, Dennis -- Zentrum für Technomathematik, AG Optimierung und Optimale Steuerung fon: 0421-218.63866 fax: 0421-218.9863866 web: www.worhp.de ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
