running tests leaves lots of coredumps
Submitted by Yeti
If coredumps are enabled then running
make check in GLib produces over 90 coredumps in various
tests subdirectories even if all tests succeed. This is due to forked tests that are expected to abort (which subsequently checked by
This is not specific to the GLib test suite; any gtester test suite containing tests that are supposed to abort will behave the same.
It is easy to disable coredumps, however, enabling them while running tests is useful in case something fails unexpectedly. So the tests should dump core only if this unexpected failure happens and not when everything goes as expected.
Steps to reproduce:
- git clone git://git.gnome.org/glib
- cd glib
- make check
- find . -name 'core*'
All tests pass and no coredumps are left.
All tests pass and 93 coredumps are left.