The topic title says it all. How do you investigate on finding bugs in your lite-c applications?

My usual method is to place a printf("before"); and a printf("after"); in the code surrounding the place where I expect the crash. Then I iteratively change the position of them so that i get closer and closer to the crash. Printing out some debug information with printf is also very usefull sometimes.

i do the same.

Me too, placeing printf("Test1"); ... printf("Test2"); ... printf("Test3"); helps to find out where the error is.

I USE A PANEL WHITE 5 VARS wit as most as possable precisesion so you can see if its like 0,001so you dont miss anything
sometimes i use a text debug

and if i can find the problem i write return to see were te problem is if the problem still is there you need to write return on a other place

and dont forget if you place return inside a loop and there is no error its in the loop

First I locate the error in a small block of code. Then I think of all possibilities that could occur making my application crash.

If I can't solve it, then I start checking all variables (pointer, numbers, more pointers, strings, again pointers) which have a relation to the false code on weird behaviour. If I detect abnormalities here, I usually find the bug soon as well.

No abnormalities? Then it's time to have a little private conversation with the piece of code. I make a copy of the whole script and cut as much unnecessary code out as possible, or replace with dummy data. Usually it will work then, and from here I try every possibility to make it crash the same way it did in the old code until I found out why.

If it does crash right after placing it within it's new scope, I start to get hopeless and post on the forum asking why my game hates me and break down in tears.