You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users may want to exit CrashMonkey before the test harness has finished a complete run. They should be able to hit ctrl-c on the shell to kill it and expect CrashMonkey to clean up resources properly.
Most of this should just be catching the proper signal and then calling cleanup_harness() in the instance of the Tester object that harness/c_harness.cpp has.
Right now, I know that background communication sockets aren't cleaned up, kernel module(s) aren't removed, and file systems aren't unmounted (depending on when ctrl-c is hit).
The text was updated successfully, but these errors were encountered:
Users may want to exit CrashMonkey before the test harness has finished a complete run. They should be able to hit
ctrl-c
on the shell to kill it and expect CrashMonkey to clean up resources properly.Most of this should just be catching the proper signal and then calling
cleanup_harness()
in the instance of theTester
object thatharness/c_harness.cpp
has.Right now, I know that background communication sockets aren't cleaned up, kernel module(s) aren't removed, and file systems aren't unmounted (depending on when ctrl-c is hit).
The text was updated successfully, but these errors were encountered: