Report more debug information about caught exception

...in an attempt to track down why various tinderbox builds started to fail
CppunitTest_sw_filters_test with an "Uncaught exception during Task::Invoke()!"
abort.

On IRC, jmux claims that catching exceptions and turning them into abort() here
(instead of letting them propagate) is necessary:  "The main problem was the
wrong state in the scheduler.  So something actually handled the exception, but
the next caller into the scheduler had an invalid linked list of tasks, breaking
things left and right."

Change-Id: Ic3365e282404483518652c00160c2036b79991cf
Reviewed-on: https://gerrit.libreoffice.org/46450
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>

0 files changed, 0 insertions, 0 deletions