>> > I *may* be having a problem with stack overflow (or underflow, for that
>> > matter), but I can't seem to nail it down with 2000 lines of code.  Can
>> > anyone suggest how this can be done?
>>
>>Both the simulator and emulator have facilities for trapping this.

I realize this, but I don't think I can fully simulate all the I/O and
interrupts for this system with the MPLAB simulator alone.  And I don't have
an ICE :(

I guess I was looking for a piece of software that could go through the code
and take all possible paths to find the maximum/minimum stack level.  This
doesn't seem like it would be that difficult a task, does it?  As I said, I
thought someone had done it already, but I can't remember who it was or what
it was called.

And since there are no registers or bits that indicate a stack overflow
while the program is running, I can't just add a LED or something to output
while running the system.  Microchip is funny in this respect; they
specifically state that stack overflow isn't indicated, yet I can't see
where it would be that tough for them to actually implement it.

--Andrew
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body