|
From: Nicholas N. <nj...@cs...> - 2005-06-29 13:35:13
|
Hi, I want to remove the "Corecheck" tool. Corecheck is just like Nulgrind, except that it turns on "core errors". These are errors that the core can detect. The main ones used to be all the pthread errors, before they were disabled. There are also some other minor ones like detecting bad signal numbers in some signal-handling functions, and detecting bogus file descriptors passed to read(). The Corecheck regtests in theory are exercising these "core errors". In practice they are not. Most of them could be moved into Nulgrind with no change. The small number that actually report a "core error" could be moved into memcheck/tests/, since Memcheck (along with Addrcheck and Helgrind) turn on "core errors". I started this move last night, moving some of corecheck/tests/ into none/tests. And since regression testing was Corecheck's raison d'etre, if I move the regression tests out of corecheck/tests/ then Corecheck might as well die. It would be one fewer tool to maintain and document. Any objections? Related to this: Nulgrind currently does report some minor errors, eg. if you pass an invalid file descriptor to read(). I think it shouldn't, that all minor errors like this should only be reported if "core errors" have been turned on in the tool. Thus Nulgrind would never report any kind of errors, just run the program normally. Memcheck and co. would still report these minor errors, of course. Any objections to this? N |