Improve EXCEPTQ trap report generation, part 2

dmik commented 3 years ago

A continuation of #98.

There are further improvements but they need changes in EXCEPTQ, this ticket is to track them:

[ ] 1. Support for extended trap report info to pass the full LIBC panic message to EXCEPTQ via EXCEPTIONREPORTRECORD::ExceptionInfo (currently LIBC abuses the short report info message for that which is only 80 chars.
[ ] 2. Put LIBC and LIBCx version into the short message once the above is done.
[ ] 3. Put all .TRP files to a single directory (e.g. /@unixroot/var/log/exceptq).

dmik commented 3 years ago

@StevenLevine BTW if you think 3 is not so easy for you, you could just support an arbitrary .TRP file name via ExceptionInfo too. So that a MYHANDLER caller could specify a full file name they want the report end up into. I personally don't think it's the best option as it will be better if all .TRP will go there, including apps using EXCEPTQ directly. But I'm ready to discuss this.

dmik commented 3 years ago

The above two commits provide a workaround that moves .TRP files to a system log location (see #101), until @StevenLevine fixes EXCEPTQ. Works good so far.

bitwiseworks / libc

Improve EXCEPTQ trap report generation, part 2 #99