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

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

Rats!  I was too optimistic about fixing the problem. . . . .

> > 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.

Yes, even if I just type "valgrind".

> > 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!!!!

Actually, the only thing this did was allow valgrind to spew a whole
bunch of cruft before segfaulting.  Here are the last few lines before
segfaulting:

22740:  symbol=_dl_map_object_deps;  lookup in file=/lib/i686/libc.so.6
22740:  symbol=_dl_map_object_deps;  lookup in file=/lib/ld-linux.so.2
22740:  
22740:  calling init: /usr/local/lib/valgrind/valgrind.so
22740:  
22740:  symbol=__register_frame_info;  lookup in file=true
22740:  symbol=__register_frame_info;  lookup in file=/usr/local/lib/valgrind/vgskin_memcheck.so
22740:  symbol=__register_frame_info;  lookup in file=/usr/local/lib/valgrind/valgrind.so
22740:  symbol=__register_frame_info;  lookup in file=/lib/i686/libc.so.6

By the way, I did put in a bunch of "echo" statements into the
valgrind script.  The place where it segfaults is when it actually
execs the invoked program at the end of the script.  It doesn't puke
for any of the environmental set-up statements. 

Does anybody have any ideas about what is wrong?

Stuart