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

..

.gitignore

gitignore tweaks

2011-07-22 15:47:24 +02:00

binding.c

more 'static' adding in testcases

2011-10-16 21:41:15 -04:00

boxed.c

various GLib tests: plug memory leaks

2011-12-14 12:40:16 +00:00

dynamictests.c

more 'static' adding in testcases

2011-10-16 21:41:15 -04:00

enums.c

gobject: Use G_VALUE_INIT

2011-10-18 17:12:33 +01:00

ifaceproperties.c

various tests: do not provoke SIGTRAP with -m no-undefined

2011-12-27 17:51:09 -05:00

Makefile.am

Improve test coverage for GValue transformations

2011-06-23 00:05:18 -04:00

param.c

GObject: do checks on interface property install

2011-12-20 19:45:57 -05:00

properties.c

more 'static' adding in testcases

2011-10-16 21:41:15 -04:00

reference.c

gobject: Use G_VALUE_INIT

2011-10-18 17:12:33 +01:00

signals.c

more 'static' adding in testcases

2011-10-16 21:41:15 -04:00

testcommon.h

Move ifaceproperties test to gobject/tests/

2010-12-27 23:49:12 -05:00

threadtests.c

more 'static' adding in testcases

2011-10-16 21:41:15 -04:00

valuearray.c

gobject: Use G_VALUE_INIT

2011-10-18 17:12:33 +01:00