|
From: Nicholas N. <nj...@ca...> - 2004-08-25 16:20:20
|
On Tue, 24 Aug 2004, Kostub Deshmukh wrote: > I am trying to run valgrind 2.1.2 on my binary and it cannot read the debugging > symbols from the binary. > > this is the error i get in the logs: > > ==4295== Startup, with flags: > ==4295== --tool=memcheck > ==4295== -v > ==4295== --log-file=valg > ==4295== Contents of /proc/version: > ==4295== Linux version 2.4.21-2.3a (root@kernel-build-101) (gcc version 2.96 > 20000731 (Red Hat Linux 7.1 2.96-98)) #1 Fri Dec 5 04:53:08 PST 2003 > ==4295== Reading syms from > /net/deshmukh.desktop/X86_LINUX_GCC2_GLIBC22/FCSpaceManConsoleServices > (0x8048000) > ==4295== warning: mmap failed on > /net/deshmukh.desktop/X86_LINUX_GCC2_GLIBC22/FCSpaceManConsoleServices > ==4295== no symbols or debug info loaded Is this a really big file, eg. 200MB+? > I saw the post for the workaround by changing the def of VALGRIND_MAPSIZE but > did not find this definition in the .c files. Yes, the code has changed and that macro does not exist any more. If you get the latest Valgrind from CVS (see valgrind.kde.org/cvs.html), I've just committed a change that will allow you to work-around this -- try reducing the value of KICKSTART_BASE in coregrind/Makefile.am from 0xb0000000 to 0xa0000000, that will hopefully fix the problem. By the way, the warning you got above isn't so important; it should only be of concern if you are getting uninformative errors due to debug information for that file not being read. N |