|
From: Tom H. <to...@co...> - 2005-02-11 12:10:55
|
Some of the boxes that I run the tests on every night have the debuginfo packages for glibc installed which means that some tests fail because they produce output that names source files in the stack trace instead of just libc-x.x.x.so or whatever. I was discussing this with Jeremy the other and he suggested adding a --ignore-debuginfo=yes switch that the test suite could use to stop valgrind looking at separated debug information. He also suggested adding a --ignore-configfiles=yes switch to ignore .valgrindrc which can also cause problems with the tests. What do people think? In one way these sound like good suggestions and they would resolve real problems with the test suite, but I'm always wary of anything which means that the tests use a different code path to normal use... If people do think it's a good idea then I'll have a look at putting it in. The other question is whether to have separate switches or a single switch to enable "test mode" or something. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |