a neat feature in glib would be a ./configure-time check for the presence of valgrind.  this would mainly be for three reasons:


1) allow use of the valgrind client API from glib test caeses.

2) define some macros for glib users to use valgrind, if available, or to do nothing if not.

3) possibly: enabling the use of valgrind calls in various places inside glib (like maybe in the slice allocator, for example).


the valgrind client API allows performing operations like marking certain memory areas inaccessible, uninitialised, etc.  it's also useful for checking things like if a memory area contains defined data (which would only really be useful in tests).