How to back trace while debugging in visual studio 2010 c++

Question

0.00/5 (No votes)

See more:

Hi all ,

i am using VS 2010 Ultimate ,

a c++ sample program writen by me throws an exception at certain point.
is there any way to back trace & find out at which point exception thrown or error occours ?
please provide me any link for the same

thanks in advance. :)

--
update moved from answer

Thanks for your replies ,

I don't want time machine Smile just some log which will tell me which function called & from where exception thrown ? , i think it is possible right ? this is for thouse unhandle exception which occours unexpectedly.

Posted 31-Jan-11 18:26pm

Vivek_Mendse

Updated 1-Feb-11 2:51am

Indivara

v2

Add a Solution

3 solutions

Solution 4

i got it , it is available in visual studio trace

Posted 26-Jun-11 22:21pm

Vivek_Mendse

Solution 1

You mean run the program backwards? I doubt that is possible (unless you have a time machine)
Why not handle exceptions in your program? That way you will know where it occurred?

Posted 31-Jan-11 19:12pm

Indivara

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**JF2015** · Accepted Answer · 2011-01-31T19:17:00

Solution 2

You could have a look at the call stack. This allows you who called the function that caused the error. See here for a short introduction:
http://msdn.microsoft.com/en-us/library/a3694ts5.aspx[^]

If you are using .NET you could use the VS historical debugging feature as described here:
http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/06/16/how-does-vs2010-historical-debugging-work.aspx[^]

You should also definitely read this great CP article that describes a lot of other debugging features:
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[^]

Posted 31-Jan-11 19:17pm

JF2015

Updated 31-Jan-11 19:39pm

v2

Comments

Sandeep Mewara 1-Feb-11 1:49am

Nice answer! 5!

Indivara 1-Feb-11 8:53am

OK, I 5'd this too. Time machines do exist after all.

JF2015 1-Feb-11 8:55am

Thanks :)

Albert Holguin 27-Jun-11 9:55am

my 5... the call stack is usually good enough for C++... and there's also TRACE statements (which I didn't see a reference to in that CP article, you'd figure that would be there)