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.
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 .
The search for people who can answer your question continues for as long as needed - until you find the answer you were looking for.
When an answer is posted by someone who was invited (byYedda or by yourself) to answer your question, their answer is marked with a yellow "invited by Yedda".
To be invited to answer other people's questions in your areas of knowledge and interest, be sure to list your favorite topics:
» My Settings › My Topics.
Of course, the more helpful your answers are, the more likely you are to be invited to future questions...
Thanks. That worked and WinDbg was able to break at one of a number of CLR exceptions.
Got an answer for kipphoward? Would you like to comment on the posted answers, or vote for the one which you think is the best?
Sign up for a free account, or sign in (if you're already a member).
Other people asked questions on similar topics, check out the answers they received:
Other people asked questions on various topics, and are still waiting for answer. Would be great if you can take a sec and answer them
