Rethrowing exceptions

[Coder Guy]

I am implementing an asynchronous handler (similar to Control.EndInvoke) and
if the other thread throws an exception, I catch it and rethrow it on the
current thread. How can I rethrow the exception on the current thread while
maintaining the stack trace? The best I've come up with is encapsulating
the exception as an inner exception. I would prefer to just rethrow the
exception directly -- no need for an inner exception.

How does Control.EndInvoke handle this?

Thanks

 

[Alberto Poblacion]

I am implementing an asynchronous handler (similar to Control.EndInvoke)
and if the other thread throws an exception, I catch it and rethrow it on
the current thread. How can I rethrow the exception on the current thread
while maintaining the stack trace? The best I've come up with is
encapsulating the exception as an inner exception. I would prefer to just
rethrow the exception directly -- no need for an inner exception.

You can rethrow the current exception writing just "throw;" instead of
"throw myNewException;".

 

[Coder Guy]

I think you missed the point. The exception is saved and rethrown on
another thread, and therefore, that won't work for me...

 

[Guest]

Once you "throw ex" rather than "throw" you lose the stack trace. So,
providing the innerException as you described is probably the only way to do
what you want, unless you want to copy everything to a new exception object.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

 

[Jon Skeet [C# MVP]]

I am implementing an asynchronous handler (similar to Control.EndInvoke) and
if the other thread throws an exception, I catch it and rethrow it on the
current thread. How can I rethrow the exception on the current thread while
maintaining the stack trace? The best I've come up with is encapsulating
the exception as an inner exception. I would prefer to just rethrow the
exception directly -- no need for an inner exception.

How does Control.EndInvoke handle this?

Are you sure that Control.EndInvoke *does* handle this? Does it appear
to replace the stack trace with the original one?