I've got MPLAB 6, and when using it with an ICD2, it very often gets
confused about which line the breakpoint is, which screwes up
debugging very badly.

On 5/6/05, Alan B. Pearce <A.B.Pearce@rl.ac.uk> wrote:
> >I've occasionally seen something that may be the same symptom.  As best I
> >can tell, MPLAB looses association between source lines and program memory
> >addresses.  I had one case like that yesterday.  I know I had the right
> >source module open, but the RUN TO CURSOR menu entry, for example, was
> >grayed out.  I tried closing and reopening the file.  Eventually I got out
> >of MPLAB, rebuilt everything (although there had been no changes), got back
> >into MPLAB, and suddenly everything worked again on that same source file.
> >This has happened a few times before and I've never been able to figure out
> >the cause.
> 
> I have seen similar too, and came to the conclusion that it thinks a given
> window has the focus (even though the title bar is not highlighted), when it
> doesn't. I have recovered the situation by working my way around all the
> windows, and eventually you find the one that thinks it has the focus, and
> then on selecting the one you actually want, the focus goes with you instead
> of staying.
> 
> --
> 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