|
From: Nicholas N. <nj...@cs...> - 2005-08-08 18:28:59
|
On Mon, 8 Aug 2005, Dennis Lubert wrote: > unfortunately valgrind cannot catch all errors, as described in some > FAQs, some (quite rare) cases are missed. Memcheck should give a warning before any seg-fault-causing memory error, though. Some programs do run differently under Valgrind, although it's not very common. For example, Memcheck pads the start and end of heap blocks with 16 extra bytes so that overruns/underruns are less likely to corrupt the heap metadata, which may allow a program to run successfully under Valgrind when it crashes normally. But Memcheck should give warnings about any such overruns/underruns, so it's unclear what the problem is. N |