|
From: Nicholas N. <nj...@cs...> - 2005-03-24 14:10:18
|
On Thu, 24 Mar 2005, Benny Cheung wrote: > Below shows the log file (including all output by valgrind, the printout > from my program has been suppressed), as you can see, the program suddenly > gets a SEGV fault without going back to valgrind before exit. > > I am wondering if this happens because my program makes use of too much > virtual memory. As you can see, I have allocated 768MB at the start of the > program. So I think it may not be a bug of the new version, but only that > valgrind does not have enough virtual memory, thus causing the SEGV fault. Even if that's the case, Valgrind should die with a helpful error message rather than just seg faulting. Benny, can you file a Bugzilla bug report? (see www.valgrind.org/support/bug_reports.html). Jeremy, I wonder if it's a problem with the secondary map changes? N |