Getting WinDbg to break on encountering the "Ambiguous match found" exception. on Yedda

Getting WinDbg to break on encountering the "Ambiguous match found" exception.

This question is related to Eran Sandler's post on the "Ambiguous match found" exception encountered in ASP.NET

I tried Eran Sandler's suggestion on using WinDbg to help find out exactly which variable is a duplicate but after attaching to the w3wp.exe process and then getting the "Ambiguous match found" exception to happen, windbg doesn't break. Could there be something I'm doing wrong with WinDbg?

Thanks

PS: I posted this same question on Eran's blog but after a recent post by Eran, I thought it would be better to ask the question here.

2 Posted Answers

Order by

Post Date
votes

Eran

441 answers

532 thumbs up

They're coming to take me away, Ha-haaa!

Advanced .NET Debugging Blog

My personal blog

Sometimes in WinDbg managed exceptions are not enabled, so the debugger won't break on them.

Unfortunately I'm not near a computer with WinDbg, so I'm doing this from memory. In one of the menus (I think Debug) there is something that is called Exceptions or Filters or something.

It should open a list of all available exception type. For Windows, all managed exceptions looks the same, so you'll need to enable the "CLR Exceptions" option and then it will break on all managed exceptions (some of which might not be the exception you are looking for).

From there you can continue with what I've written in my post.

You can look in WinDbg help about enabling and disable certain types of exceptions.

If you still need help and it doesn't help you I will be around a WinDbg and a normal computer in about two weeks and I'll help you a bit more .