Re: [Valgrind-developers] valgrind: r6640 - trunk/memcheck

[Ashley P. <as...@qu...>]

Julian Seward wrote:
> Should be be in the business of checking arguments to arbitrary libc 
> functions?  I had not realised this before, but the function wrapping
> stuff makes it possible to do that if we want.

It would be a nice thing to have although a whole heap of work to do it
properly.  Question is though should memcheck be doing this or would it
require it's own tool?  How much checking could you perform by taking
the output of "valgrind --tool=callgrind --ct-verbose=1 ..." and piping
it into another application?

There are a number of functions that are done already (malloc(-1)
anyone?) but they could be better because currently they only print an
error, not the stack and don't play well with the xml output, changing
this is another thing that's on my TODO list but I'm not sure what the
correct thing to do is...

Ashley,