Shane Nelson wrote:
> When single steping in debug it all looks ok. The registers (4
> binary values, which get compacted into BCD values, which then
> get converted to the proper led code, and the tris registers) all
> do what they should. The only thing that isn't "normal" is at
> certain points, when I right click on a section of code to be
> able to do a "run to here" sometimes the "run to here" option is
> faded. Which usually means you're NOT on a peice of code. But I
> clearly am.
>
When you changed your code, did it reassemble correctly?  The reason I
ask is because of a similar "problem" I once encountered using
Microsoft's Codeview debugger.  In that situation my C code was in 7
different modules - the Make utility was configured to compile only the
modules that had changed since the last exe had been built.  If I was
looking away from the monitor (missing an error message and the
indication that the module did NOT compile successfully) and pulled the
program into the debugger, it would use the _text_ file from my latest
editing session and the _symbol_ information from the last successful
recompile.  This resulted in breakpoints not being reached and "run to
here" not working as expected because what the debugger was running and
what I thought it was running could have been offset my one or more
lines.
--Matt
--