Thread: Issues with Valgrind...looking for something comparable

Originally Posted by stahta01

Verify you are not striping the debug values using the "-s" option or the strip command.
Verify you are NOT using optimization; that might remove some info.

Tim S.

I have the makefile set to:

Code:

CFLAGS=-Wall -g

clean:
     rm -f <progname>

When I compile this is what is shown:

Code:

$make <progname>
cc -Wall -g <progname> -o <progname>

Then I use:

Code:

$./valgrind <progname>

After this I am unable to tell where the errors are, and the output looks just like the example from the above link.

I do not think I am striping or adding optimization unless those options are set in a config file or something.

There seems to be issues with valgrind and some debian based distros [see note #2]. I tried compiling valgrind from source on xubuntu 13.04 and got this:

Code:

checking the GLIBC_VERSION version... unsupported version 2.17

Maybe that is your problem?

Try using another (stable) distro, since afaik ubuntu uses debian unstable.

Originally Posted by fnprintf

There seems to be issues with valgrind and some debian based distros [see note #2]. I tried compiling valgrind from source on xubuntu 13.04 and got this:

Code:

checking the GLIBC_VERSION version... unsupported version 2.17

Maybe that is your problem?

Try using another (stable) distro, since afaik ubuntu uses debian unstable.

Is having Valgrind worth going through all the trouble? If so I will definitely do it. I can have Slackware up and running instead of xubuntu.