title: How to ignore "possibly lost" in valgrind
body: <p>I recently use valgrind with glib(with gobject), it doesn't work very well.</p>
  
  <p>I have added <code>G_SLICE=always-malloc G_DEBUG=gc-friendly</code> in the command line,
  but there's still many "possibly lost" reported by valgrind.</p>
  
  <p>As I use valgrind in automated testsuit, so I add <code>--error-exitcode=1</code>,
  but those "possibly lost" will make valgrind exit with 1, which will
  case my test fail.</p>
  
  <p>Does anyone know how to make valgrind not treat "possibly lost" as errors.</p>