This post stems from
a discussion of stack trace problems at the
CLR team blog.
The problem
When an existing exception is thrown in the normal way with throw e, any stack trace that was recorded in it is overwritten and destroyed. This complicates debugging and logging - the stack trace seen by a top-level handler (which, in a long-running
(
Read more... )
Comments 2
---
I take that by "Purists who really want to avoid calling InternalPreserveStackTrace can use this workaround :3 " you are granting the right to use. Yet it is not clear if I have to preserve this as license :/ - An Apache2 or MIT license would be great.
---
Thanks.
Reply
Reply
Leave a comment