Useful exception stacktraces #139

New Issue

sdaveb · 2023-08-11T15:00:02Z

sdaveb commented

2023-08-11 15:00:02 +00:00

Problem Description
Exception handling only prints backtraces starting from the print_backtrace function. This is not very helpful

Proposed Solution

(if any)

-Modify exception handling so that a backtrace is captured when the exception is first thrown

Create a base exception class that can wrap any other execption, along with a stack trace.
Make sure all exceptions thrown are warpped in QWEXception or something like that

- ## Problem Description - Exception handling only prints backtraces starting from the print_backtrace function. This is not very helpful ## Proposed Solution ### (if any) -Modify exception handling so that a backtrace is captured when the exception is first thrown - [ ] Create a base exception class that can wrap any other execption, along with a stack trace. - [ ] Make sure all exceptions thrown are warpped in QWEXception or something like that

sdaveb added this to the Finalize the engine core milestone 2023-08-11 15:00:02 +00:00

sdaveb added the

task

label 2023-08-11 15:00:02 +00:00

sdaveb added this to the libFramework API project 2023-08-11 15:00:03 +00:00

sdaveb referenced this issue from a commit

2023-08-17 01:00:36 +00:00

Add wrappers around exceptions to provide stacktraces.

sdaveb referenced this issue from a commit

2023-08-30 06:03:10 +00:00

Close #139 - Useful exception stack traces

sdaveb closed this issue