|
From: Naveen K. <g_n...@ya...> - 2009-05-08 16:07:44
|
-bash-2.05b# valgrind
Segmentation fault
-bash-2.05b# valgrind -v -d
Segmentation fault
-bash-2.05b# strace valgrind
execve("/mnt/package/usr/local/valgrind/bin/valgrind", ["/mnt/package/usr/local/valgrind/"...], [/* 14 vars */]) = 0
uname({sys="Linux", node="msat", ...}) = 0
brk(0) = 0x10015000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x30018000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
----- Original Message ----
From: Bart Van Assche <bar...@gm...>
To: Naveen Kumar <g_n...@ya...>
Sent: Friday, May 8, 2009 11:30:56 AM
Subject: Re: [Valgrind-developers] cross compiling valgrind
On Fri, May 8, 2009 at 5:24 PM, Naveen Kumar <g_n...@ya...> wrote:
> I am using 3.4.1.
Which output do you get when you enable the -v and -d options, e.g.
for the command "valgrind -v -d --tool=none /bin/date" ?
Bart.
|