On Wed, Jun 22, 2005 at 04:38:42PM -0400, Jack Howarth wrote: > valgrind --tool=memcheck --leak-check=yes /usr/accelrys/I2000.3L/Linux_2_Intel_32/biosym_exe/insightII > > The executable at /usr/accelrys/I2000.3L/Linux_2_Intel_32/biosym_exe/insightII > can be used to run the program normally outside of valgrind. However when I > attempt to run it within valgrind I get the error... > > ==8055== Memcheck, a memory error detector for x86-linux. > ==8055== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. > ==8055== Using valgrind-2.1.1, a program supervision framework for x86-linux. > ==8055== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. > ==8055== Valgrind library directory: /usr/lib/valgrind > ==8055== Command line > ==8055== /usr/accelrys/I2000.3L/Linux_2_Intel_32/biosym_exe/insightII > ==8055== Startup, with flags: > ==8055== --tool=memcheck > ==8055== --leak-check=yes > ==8055== -v Don't know where the -v came up, is that the default in dag's packages or do you have valgrind aliased to valgrind -v ? > ==8055== Reading syms from /usr/accelrys/I2000.3L/Linux_2_Intel_32/exe/insight/insightII (0x8048000) > ==8055== Reading syms from /lib/ld-2.3.3.so (0x3C000000) > ==8055== object doesn't have any debug info This is not a fatal error, just valgrind informing that the library does not have debuginfo in the file nor has corresponding *debuginfo* package installed. valgrind only prints this with -v. It is always better to have debuginfo for analysis by valgrind, because then more accurate information can be provided, but it is certainly not a requirement. Jakub
