Use a debugger or install temporary stack overflow checking into your code. A good way to do this is to pre-fill the stack area of RAM at power on init time to a known pattern such as 0xC6,0x6C....0xC6. Then periodically have the software check itself to see if the deepest parts of the stack continue to have this same initialization pattern in them. Clearly if the stack area gets used to a depth greater than you expect then the init pattern gets overwritten. The trick with this method however is to catch it before the overflow comes to bite you and crashes (or resets) your program. The technique is more often useful to prove you do NOT have stack overflow as opposed to proving that you DO have it.

Michael Karas