|
From: Mayukh B. <ma...@gm...> - 2006-03-03 18:53:49
|
Julian Seward <jseward <at> acm.org> writes: > > > > One of the requirements for migrating is that my program "foo" absolutely > > needs to know that it is being run by valgrind. > > Why is that? Timing issues, or something else? > > J > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > We have a portion of our code where we try to figure out the cache-size, cpuspeed, etc., of the machine it is running on. For learning about the cache-size and miss-ratio etc, we generate larger and larger vectors. This process usually takes about a second of cpu. This part of our code is simply for precise benchmarking and QA'ing of our code. Otherwise it is useless. For some reason, valgrind (first with the cachegrind tool) didn't like this part of our code and simply choked. We got around by disabling that part of the code. Later, we tried running memcheck and again it had the same problem with this piece of code. I could try to reproduce this in a smaller C program, if you are interested. It might take me a couple of days to get to it, though. -Mayukh. |