Skip to content

Consider showing platform-specific signal value in exception cases

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


We occasionally see tests terminate via signals, and CTest simply reports e.g.

4/123 Test 0000030: server_api_describe ..........................................................***Exception: Other

It would help with debugging if instead of simply "Exception: Other", it also included the platform-specific signal value, e.g. "Exception: Other (9)" or "Exception: Other (SIGKILL)".

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information