Create proper exception/crash handler #76

Open
opened 2021-04-05 13:27:56 +03:00 by icex2 · 1 comment
icex2 commented 2021-04-05 13:27:56 +03:00 (Migrated from github.com)

Summary

Create a "good" (TBD) crash/exception handler for BT5 (or rather for inject and launcher).

Detailed description

We have had various bug reports in the past that were just about "it crashes". Often, the information the log output only indicated roughly when it crashed but not really where, e.g. memory/ip addresses. It might be helpful to have some more low level information available for debugging these things.

Benefits

Information supports debugging efforts and reduces communication overhead on bug reports.

Drawbacks

None.

Current blockers

None.

## Summary <!--- Provide a general summary of your changes in the Title above --> Create a "good" (TBD) crash/exception handler for BT5 (or rather for `inject` and `launcher`). ## Detailed description <!--- Describe your feature in detail --> We have had various bug reports in the past that were just about "it crashes". Often, the information the log output only indicated roughly when it crashed but not really where, e.g. memory/ip addresses. It might be helpful to have some more low level information available for debugging these things. ## Benefits <!--- Describe the value/benefits of the feature in detail --> Information supports debugging efforts and reduces communication overhead on bug reports. ## Drawbacks <!--- Describe any drawbacks that might be introduced with this feature --> None. ## Current blockers <!--- Describe any blockers that need to be resolved before implementing this feature --> None.
icex2 commented 2024-01-30 00:56:42 +03:00 (Migrated from github.com)
Finally addressed by https://github.com/djhackersdev/bemanitools/pull/278
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Max/djhackersdev_bemanitools#76