mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-10-02 11:56:38 +02:00
fa4792c35e
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
32 lines
753 B
C
32 lines
753 B
C
#include <glib.h>
|
|
|
|
static void
|
|
test_slice_config (void)
|
|
{
|
|
if (!g_test_undefined ())
|
|
return;
|
|
|
|
if (g_test_trap_fork (1000000, G_TEST_TRAP_SILENCE_STDERR))
|
|
g_slice_set_config (G_SLICE_CONFIG_ALWAYS_MALLOC, TRUE);
|
|
|
|
g_test_trap_assert_failed ();
|
|
}
|
|
|
|
int
|
|
main (int argc, char **argv)
|
|
{
|
|
/* have to do this before using gtester since it uses gslice */
|
|
gboolean was;
|
|
|
|
was = g_slice_get_config (G_SLICE_CONFIG_ALWAYS_MALLOC);
|
|
g_slice_set_config (G_SLICE_CONFIG_ALWAYS_MALLOC, !was);
|
|
g_assert_cmpint (g_slice_get_config (G_SLICE_CONFIG_ALWAYS_MALLOC), !=, was);
|
|
g_slice_set_config (G_SLICE_CONFIG_ALWAYS_MALLOC, was);
|
|
|
|
g_test_init (&argc, &argv, NULL);
|
|
|
|
g_test_add_func ("/slice/config", test_slice_config);
|
|
|
|
return g_test_run ();
|
|
}
|