Try looking at the code using the "Disassembly Listing". You can see both 
the C and generated assembly code and the simulator will operate on the 
assembly code.

----- Original Message ----- 
From: "Alan B. Pearce" <A.B.Pearce@rl.ac.uk>
To: "Microcontroller discussion list - Public." <piclist@mit.edu>
Sent: Monday, May 09, 2005 3:21 AM
Subject: Re: [PIC] Using C with picmicro ?


> >When I used debug mode, and tried to single-step, etc. the pointer
>>just stayed put.  Don't know if this is because it wasn't the
>>microchip C compiler - it was CC8E, but the debugging functions seemed
>>quite useless without seeing where it was going
>
> I suspect what you see here is the same effect as you get using macros in
> ASM. The debug pointer cannot keep track through the macro, and leaves the
> pointer on the first line of the code, because that is where the source 
> line
> points to. The pointer does not step until you go into the next source 
> code
> line, and then it moves the whole dose of code generated by the macro you
> have just stepped through.
>
> The C code statements get treated like ASM macros I believe. It is
> definitely an area where MPLAB needs an update.
>
> -- 
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
> 


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist