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.
Hi,
Here's the required output
*[172:~]$ /usr/bin/valgrind --trace-syscalls=yes --trace-symtab=yes
--trace-syb-patt=/usr/lib/mylib.so.debug /usr/bin/myprog*
*==2944== Memcheck, a memory error detector*
*==2944== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.*
*==2944== Using
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
--2990-- Considering /usr/lib/mylib.so.debug ..
--2990-- .. CRC is valid
The above statements are the last 2 statements of the whole output. Valgrind
gets stuck here everytime ...
The valgrind version is: *valgrind-3.6.1*
and the Linux OS is based off of: *montavista*
You haven't
On Thursday, February 23, 2012, John Reiser wrote:
--2990-- Considering /usr/lib/mylib.so.debug ..
--2990-- .. CRC is valid
Based on what you did say, it is somewhat likely that valgrind got confused
by the debugging info in your executable program. Find a program which
prints out
On Fri, 2012-02-17 at 16:01 -0800, Richa Mehta wrote:
Hi,
I am a valgrind user, and while running valgrind on my program, it got
stuck on one of my library files.
Following is the output of the running valgrind:
--2990-- Considering /usr/lib/mylib.so.debug ..
--2990-- .. CRC is
