Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using a .NET app written by someone else, and I can see that’s its refreshing very slowly today. Using Process Explorer, I see that its throwing thousands and thousands of exceptions (which are presumably being caught somehow by the app).
Is there any way to see what type of exceptions these are if I don’t have access to the source code? Process Explorer only has a “# of Exceps Thrown” counter. But is there any tool out there that could tell me?
Attach the debugger to the process and you should be able to tell what the exceptions are – just not where they came from in the source code.
Make sure the exceptions settings are set appropriately. Even without this, you can always see first-chance exceptions that are caught and ignored by the app in the Output window. It’s possible this is a legitimate but ill-advised “handle error by throwing” codepath that the app hits.
If you don’t have debug access to the machine then Process Dumper can be installed and produce a full or minidump from the target process (by .EXE filename) on selected or all exceptions. I don’t think this works with managed exceptions, though. The debugger will work with both managed and native exceptions.