|
From: Xavier W. (OSIRIS-EDF) <xav...@de...> - 2005-03-17 10:21:34
|
Hi I try to use valgrind 2.2 to debug an application launched by python. valgrind --tool=memcheck --workaround-gcc296-bugs=yes --error-limit=no python MainExpert.py My program written in C++ named risk.so (loaded by python) can't be mapped : warning: mmap failed on /local/xwarin/electricity_derivatives-1-1-1/ED/Risk-BU/lib/risk.so ==16896== no symbols or debug info loaded It is a huge .so file : due to debug information it grows to 400 MB I looked into the mailing list and saw that i could change a variable KICKSTART_BASE to 0xa0000000 in coregrind/Makefile.am. I tried this fix up but it didn't improve. Any idea ? Should i take the latest snapshot of the code or an older valgrind version. Thanks Xavier |
|
From: Igmar P. <mai...@jd...> - 2005-03-18 09:09:45
|
> Any idea ? Should i take the latest snapshot of the code or an older > valgrind version. Get 2.4.0rc4, that should probably fix it. Igmar |
|
From: Nicholas N. <nj...@cs...> - 2005-03-18 15:30:20
|
On Thu, 17 Mar 2005, Xavier WARIN (OSIRIS-EDF) wrote: > My program written in C++ named risk.so (loaded by python) can't be mapped : > warning: mmap failed on > /local/xwarin/electricity_derivatives-1-1-1/ED/Risk-BU/lib/risk.so > ==16896== no symbols or debug info loaded > > It is a huge .so file : due to debug information it grows to 400 MB > I looked into the mailing list and saw that i could change a variable > KICKSTART_BASE to 0xa0000000 in coregrind/Makefile.am. > I tried this fix up but it didn't improve. > > Any idea ? Should i take the latest snapshot of the code or an older valgrind > version. It probably won't make that much difference; this mis-handling of large .so files is still an unfixed problem (see bugs.kde.org/show_bug.cgi?id=82301). You could try moving KICKSTART_BASE lower, eg. 0x90000000, that might work. N |