You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now lv2 is just crashing, rebooting or going into an infinite loop when a userspace program encounters an exception.
This isn't very useful.
At the very least it should kick the user back to the xmb, Even better, it should allow the program to register a handler that will get called when an exception is encountered so the program can exit correctly.
The text was updated successfully, but these errors were encountered:
I plan to do that lowlevel task (after finishing msgDialog stuff) in a PSL1GHT app:
Replacing all FW3.41 LV2 Exception Handlers (Machine Check/DataStorage/DataSegment/InstructionStorage/InstructionSegment/Alignment/Program and also Trace Exception), with optional user API to manage them by any Apps.
Right now lv2 is just crashing, rebooting or going into an infinite loop when a userspace program encounters an exception.
This isn't very useful.
At the very least it should kick the user back to the xmb, Even better, it should allow the program to register a handler that will get called when an exception is encountered so the program can exit correctly.
The text was updated successfully, but these errors were encountered: