When exceptions are rethrown with throw ex;, the original context (the stack) is lost
#5
Comments
lefth
pushed a commit
to lefth/Unity3dAsyncAwaitUtil
that referenced
this issue
Apr 12, 2018
When an exception is thrown again ("throw ex"), its stack will be
overwritten. Instead, it should be rethrown with its original context.
More info here (Figure 2):
https://msdn.microsoft.com/en-us/magazine/mt620018.aspx
Issue modesttree#5
lefth
pushed a commit
to lefth/Unity3dAsyncAwaitUtil
that referenced
this issue
Apr 12, 2018
When an exception is thrown again ("throw ex"), its stack will be
overwritten. Instead, it should be rethrown with its original context.
More info here (Figure 2):
https://msdn.microsoft.com/en-us/magazine/mt620018.aspx
Issue modesttree#5
lefth
pushed a commit
to lefth/Unity3dAsyncAwaitUtil
that referenced
this issue
Apr 12, 2018
When an exception is thrown again ("throw ex"), its stack will be
overwritten. Instead, it should be rethrown with its original context.
More info here (Figure 2):
https://msdn.microsoft.com/en-us/magazine/mt620018.aspx
Issue modesttree#5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the exception is cached and
throw;is not applicable, another technique is needed to preserve the original exception's context. Storing it as anInnerExceptionis one way, but I think in this case, it's more useful to rethrow it without changing its context:A pull request is on the way.
The text was updated successfully, but these errors were encountered: