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
To improve the descriptiveness of runtime errors and faults, we should modify the error handling in some way which allows the calling application to trace the call stack and determine the instruction that triggered a fault. Some information about the state of registers and the stack (similar to a core dump) would also be useful.
This will help users debug RVM code as well as enable us to find flaws in the VM itself.
The text was updated successfully, but these errors were encountered:
I've began working on the new ResurgenceError object. As I'm going to Pakistan for Thanksgiving break this will be a fun thing to test and perfect on the way
To improve the descriptiveness of runtime errors and faults, we should modify the error handling in some way which allows the calling application to trace the call stack and determine the instruction that triggered a fault. Some information about the state of registers and the stack (similar to a core dump) would also be useful.
This will help users debug RVM code as well as enable us to find flaws in the VM itself.
The text was updated successfully, but these errors were encountered: