Files
glib/gio
Simon McVittie fa4792c35e various tests: do not provoke SIGTRAP with -m no-undefined
Some of the GLib tests deliberately provoke warnings (or even fatal
errors) in a forked child. Normally, this is fine, but under valgrind
it's somewhat undesirable. We do want to follow fork(), so we can check
for leaks in child processes that exit gracefully; but we don't want to
be told about "leaks" in processes that are crashing, because there'd
be no point in cleaning those up anyway.

https://bugzilla.gnome.org/show_bug.cgi?id=666116
2011-12-27 17:51:09 -05:00
..
2011-12-10 17:23:28 -05:00
2011-12-08 18:05:14 -05:00
2011-08-29 14:49:32 -04:00
2011-10-18 17:12:33 +01:00
2011-06-04 19:05:51 -04:00
2011-08-29 14:49:32 -04:00
2011-06-14 21:06:17 -04:00
2011-10-18 17:12:33 +01:00
2011-12-10 21:55:11 -05:00
2011-12-17 12:54:02 -05:00
2011-08-29 14:49:32 -04:00
2011-12-08 18:05:13 -05:00
2010-06-04 19:03:38 +02:00
2011-06-04 18:48:19 -04:00
2011-08-29 14:49:32 -04:00
2011-08-04 08:54:55 +02:00