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 now debugging a program that utilizes many different threads.
There is an exception that is thrown from time to time. The problem is that there is no way to know what thread caused the problem…
Is there an easy way to get the stack trace after the exception is thrown?
I thought about simply writing a debug messages, but it is going to be a huge 🙂 I guess there are much better techniques than this one …
I’m using Visual Studio 2008 – native C++ project….
Unless I’m very much mistaken, you need to know which thread triggered the exception in order to use the Visual Studio debugger’s call stack view, which is obviously the catch-22 situation you’re in at the moment.
One thing I would try is to see if you can get the debugger to break when the exception is thrown (using Debug > Exceptions). You’ll have to explicitly enable this, but if you know what type of exception is thrown, this might allow you to work out where it’s thrown.
Other than that, putting a breakpoint in the constructor of the exception (if it’s one of your own) should also allow you to work out where it’s triggered from.
If those methods don’t work for you I’d be looking at the debug messages as you already suggested.