>A further advantage of doing this in the assembler is that XCASM 
>can generate a profile of the executable which shows all the 
>execution paths through an instruction. With this you can easily 
>work backwards and identify paths through an instruction that you 
>had not anticipated or simple forgotten about. This greatly helps 
>locate an execution path where a variable (or SFR) is undefined.
>This is the kind of error you normally use a simulator and trace 
>buffer to find, but with this kind of debugging you might need to 
>spend hours homing in on the problem path.

Whew, with all this, will it also act as a disassembler ?
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist