At 03:36 PM 4/28/2008, you wrote:
>I have not used PICC Lite, but have instead used Microchip's C18 and C30.
>Someone pointed out that optimization may cause variables to disappear. I
>have not seen that, but have seen wild program line execution order when
>single stepping if I have full optimization on. For debug, I either turn
>off optimization or set it to "debug."
>
>I am also not familiar with the fakelocal flag, but I expect that it makes
>local variables static instead of automatic so they have a permanent
>location in RAM instead of a location on the stack. You do not indicate
>whether the problem is with global or local variables (apparently it's
>with both since you have the button grayed out). I have not ever seen that
>happen.
>
>With C18 and C30, local variables are visible in the watch window when you
>are in the function they are defined in. If you step outside the function,
>the watch window says they are out of scope. Global variables are always
>visible.
>
>So... Since I have not use PICC Lite, I am not really answering your
>question. There are some general comments on the watch window, though.
>
>Good luck!
>
>Harold

One general suggestion I have is to avoid paths to the project directory
that are very long or have spaces in them. Some programs still have problems
with such things. Try re-creating the project in a folder such as 
C:\myproject\
and see what happens.

>Best regards,

Spehro Pefhany --"it's the network..."            "The Journey is the reward"
speff@interlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com



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