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
With Takipi's UI, users are able to walk the stack and see the value of the variables for the caller methods as well, additionally to the method where the exception happened.
This could be done with GW too by storing references to the caller methods' context variables and sending them over the wire at the time of an exception.
Additionally, the depth of the storage could be set before compilation with the default of n=3 or n=4.
In theory, this should not impact performance significantly because storing the reference has small footprint. Nevertheless, it has to be tested when the feature is implemented.
The text was updated successfully, but these errors were encountered:
With Takipi's UI, users are able to walk the stack and see the value of the variables for the caller methods as well, additionally to the method where the exception happened.
This could be done with GW too by storing references to the caller methods' context variables and sending them over the wire at the time of an exception.
Additionally, the depth of the storage could be set before compilation with the default of n=3 or n=4.
In theory, this should not impact performance significantly because storing the reference has small footprint. Nevertheless, it has to be tested when the feature is implemented.
The text was updated successfully, but these errors were encountered: