Hi, With both releases 3.6.0 and 3.6.1, I have noticed that valgrind almost always segfault on my RedHat-4 x86_64 machine.
It seems that it works when running a 32 bits program, and fails when running a 64 bits one. For instance: $ valgrind /bin/ls ==18112== Memcheck, a memory error detector ==18112== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==18112== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info ==18112== Command: /bin/ls ==18112== Segmentation fault (Obviously, /bin/ls works when not executed through valgrind ;-) $ file /bin/ls /bin/ls: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped $ valgrind /path/to/32bits/bin/ls [ls output is OK] What can I do to track down this problem, and maybe post a bug report with enough useful information? Thanks, Christophe. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
