Re: [Valgrind-users] Immediate segfault with valgrind-1.9.5 on RH7.1

[<sd...@cl...>]

Hi --

> On Mon, 28 Apr 2003, Stuart Brorson wrote:
> 
> > With great anticipation I downloaded and built valgrind-1.9.5 last
> > night.  I did a vanilla "./configure ; make ; make install".  When I
> > tried "valgrind ls -l", I got "Segmentation fault (core dumped)".
> > Rats!  When I run valgrind alone, I also get a segfault.
> 
> You mean even if you just type "valgrind"?  Weird... something must going
> wrong in Valgrind's startup shell script.
> 
> Can you try fiddling with $PREFIX/bin/valgrind, inserting some debug
> "echo" statements to work out where exactly the seg fault is happening?
> 
> N

OK, I fixed my problem.  I examined /usr/local/bin/valgrind.  It
turned out that at one  place in that script I had:

#LD_DEBUG=files
#LD_DEBUG=symbols
#export LD_DEBUG

This is how "make ; make install" created the script.  When I
uncommented "LD_DEBUG=symbols", and "export LD_DEBUG" valgrind started
working.  Yay!!!!

Now my only question is:  why did the default install procedure create
a script with this option commented out?  Or did I just not RTFM?

Stuart