From: Richa M. <ric...@gm...> - 2012-02-23 18:26:46
|
Hi the output of valgrind ls -l is: ************************************************************************************************************ [172:~]$ /usr/bin/valgrind ls -l ==2096== Memcheck, a memory error detector ==2096== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==2096== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info ==2096== Command: ls -l ==2096== total 5296 -rwxr-xr-x 1 root root 2119 Feb 17 20:21 STARTMYPROC -rwxr-xr-x 1 root root 3107672 Feb 17 20:21 _mydope.so -rwxr-xr-x 1 root root 23211 Feb 17 20:21 mydope.py -rwxr-xr-x 1 root root 23173 Feb 17 21:21 mydope.pyo -rwxrwxr-- 1 root root 3432 Feb 20 21:01 stack-mgr.log -rwxr-xr-x 1 root root 23859 Feb 17 20:21 stack_mgr.py ==2096== Invalid free() / delete / delete[] ==2096== at 0x48CE3E8: free (replace_malloc.c:366) ==2096== by 0x4A10B1B: free_mem (in /mylib/libc-2.11.1.so) ==2096== by 0x4A10659: __libc_freeres (in /mylib/libc-2.11.1.so) ==2096== by 0x48C8493: _vgnU_freeres (preloaded.c:62) ==2096== by 0x4996AA7: _Exit (_exit.S:30) ==2096== Address 0x48cae00 is not stack'd, malloc'd or (recently) free'd ==2096== ==2096== ==2096== HEAP SUMMARY: ==2096== in use at exit: 12,656 bytes in 20 blocks ==2096== total heap usage: 105 allocs, 86 frees, 23,131 bytes allocated ==2096== ==2096== LEAK SUMMARY: ==2096== definitely lost: 0 bytes in 0 blocks ==2096== indirectly lost: 0 bytes in 0 blocks ==2096== possibly lost: 0 bytes in 0 blocks ==2096== still reachable: 12,656 bytes in 20 blocks ==2096== suppressed: 0 bytes in 0 blocks ==2096== Rerun with --leak-check=full to see details of leaked memory ==2096== ==2096== For counts of detected and suppressed errors, rerun with: -v ==2096== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 22 from 9) [172:~]$ ****************************************************************************************************************** This shows that valgrind is working properly.... On Wed, Feb 22, 2012 at 7:12 PM, David Chapman <dcc...@ac...> wrote: > On 2/22/2012 6:43 PM, Richa Mehta wrote: > > Hi, > > The valgrind version is: *valgrind-3.6.1* > and the Linux OS is based off of: *montavista* > > I first connect to a virtual machine (VM), boot up my build image without > starting any services. > Then I run valgrind on my process, (only after starting all the services > on which my process is dependent, so there is no dependency issue) > Now, once the valgrind runs, it gets hung. > > I tried using all the flags including -d, -v, --leakcheck, etc > once it gets hung, I am not even able to access the log file. > > I also tried to ssh to the vm which runs valgrind and the only thing I > could figure out fro it is 2 to 3 processes taking more space... > I don't think this will be of any help > > Can u plz guide me as to how to access the log file of valgrind, once it > gets hung. Atleast that might give me some info as to which thread is > causing the problem. > > > What happens if you launch valgrind on the command "ls -l"? Does valgrind > fail every time on the VM, or just on your program? > > -- > David Chapman dcc...@ac... > Chapman Consulting -- San Jose, CA > Software Development Done Right. > www.chapman-consulting-sj.com > > -- *Regards* *Richa Mehta* *MS, Computer Engineering* *Santa Clara University* |