🔒 Locked

Debugging question

Started by The C modest god Aug 30, 2005 at 1:24 PM 3 replies 400+ views

Original Post

112

Aug 30, 2005 at 1:24 PM

I have found a bug of an infinite loop in my code. So I fixed it. However, what bothers me is that when I did go in debug mode and then did break. The call stack showed that I was in KERNEL and INPUT8 instead inside the problematic loop. Why does that happen? Is it because of the alt tabbing to go to visual and do the break? Why this happen?

Anon Mike

117

Anon Mike

Aug 30, 2005 at 1:30 PM

Need to see some code. Knowing your OS and debugger would help too.

CTar

113

CTar

Aug 30, 2005 at 1:31 PM

It's probably because those functions are called from the infine loop, imagine:

void Draw(){    SetMatrices();}void SetMatrices(){    VectorStuff();    VectorToMatrix();}void VectorStuff(){}void VectorToMatrix(){}int main(){    while(true)    {        Draw();    }    return 0; }

When you break you might be in VectorToMatrix since the calls go like this;
main->Draw->SetMatrices->VectorToMatrix
You should be able to "jump" down and see what is happening in the main loop by using the callstack, for example if it looks like this:
VectorToMatrix
SetMatrices
Draw
main

You should be able to double-click main and know you are in the loop. At least this is how it works in MSVC7.1

The C modest god

Author

112

The C modest god

Aug 31, 2005 at 3:18 PM

No, the callstack does not contain any of my code, in any upper level.
I don't have now this code because I did major modifications.
I guess this will remain a mystery

mattnewport

Aug 31, 2005 at 3:21 PM

You probably broke into the wrong thread. Go to the 'threads' debugger window and you can choose which thread you wish to view the callstack for.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.