|
From: Tom H. <to...@co...> - 2009-05-07 21:30:35
|
Karlan Mitchell wrote: > I haven't really taken the time to dig through the source code to verify > this however, > I have noticed that some programs which segfault run by the kernel fail > to do so > when run by valgrind, and occasionally gdb. The only thing I can guess > off the top > of my head is the code running makes bad assumptions, or memory errors, > which only > fails when that code is non-zero. / The memory map will be completely different under valgrind, plus valgrind deliberately spaces out heap allocations so that a minor under/overrun will probably not crash the program (but will of course produce a valgrind warning). Programs which segv will not always do so reliably even without bringing valgrind into the equation, so it really isn't something you should worry about. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |