|
From: Todd B. <to...@ns...> - 2003-09-24 15:20:42
|
Hi Everyone, I'm new to Valgrind, so I appologize if this is already known. I am compiling some code which links in some third party libraries (TIFF, GeoTIFF, Proj4). I wanted to link in the static (.a) libraries instead of the shared so I linked the code using the -static flag. When linked this way, Valgrind seems to ignore the program producing no valgrind output whatsoever. I recompiled the code removing the -static flag and valgrind works fine. In this process, I found that I had already removed the shared (.so) libraries anyway, so the static flag was unnecessary. So effectively, the same libraries are linked in to the code, but Valgrind does not work if -static is specified on the link line. By the way, I have been a longtime user of Purify and I must say that I am very impressed with Valgrind. Valgrind functions much like the Purify I used to use on SGI. I have Purify Plus on Linux, and it is not the same as the IRIX (SGI) version. It requires recompilation and source code modification and just plain doesn't work as well as the old IRIX version. We are mothballing our old SGI's and I was worried about what I would do about Purify. Valgrind has answered that question for me. I am not going to renew my maintanence for Purify and am switching to Valgrind. Sincerely, Todd -- __________________________________________ Todd Berendes Research Scientist National Space Science & Technology Center University of Alabama in Huntsville 320 Sparkman Drive Huntsville, AL 35805 (256) 961-7943 fax:(256) 961-7755 to...@ns... __________________________________________ |