On Sun, Jun 1, 2008 at 8:58 PM, Pavel Roskin <proski@xxxxxxx> wrote: > On Sun, 2008-06-01 at 20:42 +0200, Vegard Nossum wrote: > >> None of these produce errors or even warnings when they are run >> through sparse. I probably won't get around to fixing these myself >> since I'm not that familiar with sparse internals. This is just a >> heads up :-) > > Still, you may be able to create test cases for the testsuite. Ah, that's be true. I have now submitted the .c files that should produce the errors/warnings, but I can't seem to find an actual testsuite in which to hook them. The existing test-* files seem to test the API, not the files to be parsed. Vegard -- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036 -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
