|
From: Nicholas N. <nj...@cs...> - 2005-05-06 13:20:49
|
On Wed, 4 May 2005, Naba Kumar wrote:
> void
> update_callback (ValgrindRecord *r, other info ...)
> {
> switch valgrind_record_get_type (r)
> {
> case VALGRIND_RECORD_MEMLEAK:
> ... update mem leak report ...
> case VALGRIND_RECORD_MEMCORRUPT:
> ... update mem corruption report ...
> }
> }
>
> [snip]
>
> I understand that valgrind could not be operated in the same process
> space as the main program and hence the difficulty in making it a
> library. It's one unfortunate situation that I hope you people could
> come around :).
Yes, that is a challenge. Something like a socket-based approach, passing
packets describing errors, could be the way to do it. I wouldn't hold
your breath for someone to implement it, though, since there has been
little demand for such a thing so far.
N
|