This, since it was discovered using the Cygnal ICE, is posted at the SILabs forum as well

I have, for who knows how long, always prefaced local variables with a 3 letter 'abbreviation' of the function they were in, that has served me well here is an example:

void ConvertColor(void)
{
U8  CVCCcolor;

now I was inserting some debugging code and ignored my 'rule' since the code was "fast and temporary, to be discarded".
Well I spent too long time in the debugger till I found out that if two funtions have an identically named variable, you can get caught in a real quagmire: If you set a watch of variable 'ralph' in func1 and func 2 also has a variable 'ralph' and you watch 'ralph' in func2, you are screwed.
I would NOT consider this an error in the debugger.

Coming to think of it, I guess I developed the naming convention running into a similar problem with another debugger in the days when Cygnal still "was a glint in the founders eye"

So, I will adhere religously to my 'standard' and if you want to pick it up, you are welcome. At least now you are aware of the potential trap from identically named local variables.

Erik