|
From: Igmar P. <mai...@jd...> - 2003-08-05 13:54:02
|
> And that's the point, in this case valgrind knows, that the access after > this invalid read will cause a > Core dump, because you try to access a Null-Pointer and that it should tell > the user. Why all this trouble for a NULL pointer dereference ? If you can't debug those, you can't debug the rest. Most weird cores happen when doing something else, like double free()'s, screwing up TLS when using pthread's, etc. Adding code if thing would core is a a huge job to do. Most valgrind related core's I've seen come after a valgrind assert. > I really think valgrind is as great a memory checker as there is for free to > get, but it needs on some > Edges a little bit more work. > I'am working in a medium sized firm, and have installed valgrind for all of > our programmers, but some of them would always seek the fault by someone > else, before thinking that they could have made a fault... Reeducate your programmers. Take my word, valgrind cores are rare and mostly obvious. It it cores with valgrind, it usually also does without. Igmar |