diff options
author | Jens Freimann <jfreimann@redhat.com> | 2017-08-08 22:38:59 +0200 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2017-08-09 04:22:14 +0300 |
commit | 24dd1e17696fbd11b3df50718dddcbdfe2c45f24 (patch) | |
tree | a47e36f4fe6dad3c0361032ff552ebb0ce9eb1b6 /tests/acpi-test-data/q35/DSDT | |
parent | 2566378d6d13bf4d28c7770bdbda5f7682594bbe (diff) | |
download | qemu-24dd1e17696fbd11b3df50718dddcbdfe2c45f24.zip qemu-24dd1e17696fbd11b3df50718dddcbdfe2c45f24.tar.gz qemu-24dd1e17696fbd11b3df50718dddcbdfe2c45f24.tar.bz2 |
libqtest: always set up signal handler for SIGABRT
Currently abort handlers only work for the first test function
in a testcase, because the list of abort handlers is not properly
cleared when qtest_quit() is called.
qtest_quit() only deletes the kill_qemu_hook but doesn't completely
clear the abrt_hooks list. The effect is that abrt_hooks.is_setup is
never set to false and in a following test the abrt_hooks list is not
initialized and setup_sigabrt_handler() is not called.
One way to solve this is to clear the list in qtest_quit(), but
that means only asserts between qtest_start and qtest_quit will
be catched by the abort handler.
We can make abort handlers work in all cases if we always setup the
signal handler for SIGABRT in qtest_init.
Signed-off-by: Jens Freimann <jfreimann@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'tests/acpi-test-data/q35/DSDT')
0 files changed, 0 insertions, 0 deletions