|
From: Yuri <yu...@ts...> - 2005-01-26 11:38:57
|
I was able to figure out the answer myself: I changed variable KICKSTART_BASE = 0xb0000000 to KICKSTART_BASE = 0xa0000000. This brought available space between valgrind_base and valgrind_end to 512MB. Now my executable fits. But error messages were not particularly strong, noone said "Out of memory" or alike. Just "mmap failed" which is confusing since it's really not an OS mmap. I think error messages have room for improvement. Yuri. Yuri wrote: > I am running --tool=callgrind on my executable, runs fine but doesn't > load debug info. > I debugged valgrind itself and found that VG_(find_map_space) called > from VG_(mmap) > returns null and further analysis and enabling of printout showed that > executable with debug info is loaded into [valgrind_base - > valgrind_end] space and memory limits are: > > client_base 0 (937MB) > client_mapbase 3A965000 (1877MB) > client_end AFF00000 (1MB) > shadow_base B0000000 (0MB) > shadow_end B0000000 (0MB) > valgrind_base B0000000 (255MB) > valgrind_end BFFFFFFF > > and my executable is 271,272,753 bytes (with debug info). > > Is it a way to still load debug info for my 270 MB executable ? > > Thanx, > Yuri > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |