When using windbg is there a way to break on a specific CLR exception

Question

I'm debugging a production service which is at rare instances is throwing AppDomainUnloadedException. The exception contains no stacktrace or any kind of useful information about why it happens. So want to attach windbg and only break when AppDomainUnloadedException is thrown and not any other clr exception.

Is this possible?

I don't know how to do it in windbg, but have recently done it with mdbg. See my blogpost: nickvane.blogspot.com/2011/07/… . Instead of using 'ca ex' you could use 'ca AppDomainUnloadedException' — nickvane
– nickvane, Commented Jul 27, 2011 at 12:26
Thanks, that worked for all other exception, except the one I was trying to catch. :( It does how ever gets caught by the UnhandledException handler but without a stacktrace or any other useful information. — Christian
– Christian, Commented Jul 28, 2011 at 14:20

StayOnTarget · Accepted Answer · 2020-10-30 14:36:49Z

8

You're look for the !soe command (Stop On Exception) syntax should be something like:

!soe System.AppDomainUnloadedException 1

edited Oct 30, 2020 at 14:36

StayOnTarget

13.4k11 gold badges66 silver badges117 bronze badges

answered Jul 28, 2011 at 14:15

SamuelWarren

1,45913 silver badges30 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

kiewic Over a year ago

How can I revert the !soe command? I want to break again in all the exceptions.

Collectives™ on Stack Overflow

When using windbg is there a way to break on a specific CLR exception

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related