Two not-quite-related anecdotes that may be worth considering if there are no other clues. 1. An 18LF45K22 and a REAL ICE. The watch window allows you to enable real time watch on certain variables, but MPLAB crashes when you try it. I opened a ticket with Microchip, and the response was that the feature was anticipated in the future, but wasn't currently available. Well, thanks for making it look like it should work. You may want to ask them about your stack monitoring. I don't necessarily trust them to "grey out" things that don't work! 2. Long ago, when MPLAB didn't have the "determine programming range automatically" feature, I had limited the programming range to make the part program faster. Later, the code grew to beyond this range. So my program image in the PIC had blank regions. The resulting behavior was a lot like you described. At the very least, remember that the settings under "Debug" are separate from those under "Program" in MPLAB. Barry On Wed, Jul 25, 2012 at 8:55 PM, Harold Hallikainen wrote: > Does the hardware stack window in MPLAB 8.80 work with REAL ICE and an > 18f46k20? I have some code (mix of assembly and C) that runs at runtime, > but blows up on the debugger. Single stepping through it, it's getting to > a call of _do_cinit(), but on the return, it dumps to some random locatio= n > in my code instead of where it should. So, I figured I'd look at the > hardware stack to see what's there. The hardware stack window is always > empty, even on the call to _do_cinit. > > So, does the hardware stack window work? Any other ideas as to what could > be going on here? > > Thanks! > > Harold > > --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .