David Novak wrote:
> Does anyone have a trick to force variables to be listed?

Temporarily make them global based on a debug switch?

That's what I do in assembly now that COD files are no longer supported and
both the COFF and ELF formats keep MPLAB from showing locals not in the
current module.

I really wish they would fix this.  Yes, I know they are "out of scope", bu=
t
that's a build issue not a debugging issue.  If a variable is statically
allocated then I should be able to see its value regardless of where
execution currently is.  After all, I can look at that memory location if I
figure out what it is, just not reference it by its name.  If multiple
locals have the same name, then I can live with this either working as it
does now or require some qualification by module to display the variable.

Note that in C not seeing locals is yet another issue.  Unless you do
something special, you local variables are likely "automatic" in C lingo,
meaning they are not persistant and don't have a fixed address.  Those may
not exist unless execution is within that routine or one called by it.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.