Welcome back.
In the previous lesson we saw how to search for in on your records and how to set break.
In this lesson we are going to learn the third way which is to examine the casting and then to celebrate
points on the address.
So let's begin
Randy correct me program from the excessive for the BJP
and then take on mutton run.
Press F nine to run to the entry point.
And then run again.
O F nine and the window program starts So now enter anything.
And then click on button check and you will get a message box showing up showing the wrong zero key
message.
So I just point immediately click on the post button here.
And then from here you go through the costing.
It is very important to clean the pass button then go to the to say it passed but then it passed the
debugger.
So now you go to the casting and click on it.
And here you will see a list of all the calls that has been made since the program started.
And you can trace it.
The first call was made by system.
Then the second call also system and so on and you can see all the way up here and there is one call
which is made by the user my new which is this one here from two.
So these are modules of under the column from and is making a call to the system so this was the last
call that came from the user my you guessed before the message box was shown.
So this is the one we want to trace.
So you can select this correctly and follow from so he can follow to be used to follow this column is
right.
You can follow from his to follow the from column which is this address.
So the one we won at this point is from.
So click follow from any region to the location of the car.
So the address normally will be the one just before the address shown here which is this one.
So this is the last call that was made from the user space to the system so we can see it is correct.
This was the message box I was showing the error message box and the car is a call to show this error
message.
And now you can put your breakpoint anyway in the usual way and examine the code.
So this is how you can use the stack to search for the to trace the call that produced the error message.
And don't confuse this costing with the stack down here the state down here is the temporary memory
location used by each of the calls but this can't stay is the history of calls history or the calls
that has been made by the program so that's all for this lesson.
Thank you for watching.