Post by thread:[PIC:] Source tracking in MPLAB (was: "Re: [PIC:]

Ben Hencke <spam_OUTPICLISTTakeThisOuTmitvma.mit.edu> wrote: > I want the debugger to keep the code and really > execute it, but to cursor over it as if it was either > a function or a single instruction. The way it behaves > now is that the run cursor doesnt get to the if, it > goes straight into the macro code, so you cant even > tell what you are 'if'ing. Ben: It's been a long time since I've used MPLAB, but I remember being annoyed by that, and I have a vague recollection that there was a way to keep it from happening. Maybe if you assemble with macro expansion turned on (or off)? Try the "EXPAND" and "NOEXPAND" directives and see if that makes a difference. You might also try using "Step Over" instead of "Step"; perhaps it works with macros the way it works with subroutines. I know there's also a "track source code" checkbox in one of MPLAB's Options dialogs, but I think it affects ALL source-code tracking, not just tracking of macros. -Andy === Andrew Warren -- .....aiwKILLspam@spam@cypress.com === Principal Design Engineer === Cypress Semiconductor Corporation === === Opinions expressed above do not === necessarily represent those of === Cypress Semiconductor Corporation -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listservKILLspammitvma.mit.edu with SET PICList DIGEST in the body