I'm referring to the variables listed in the "Debugger" panel in the tab "Locals." Mostly, it does seem that when a variable changes, its updated value will then be reflected, and its name will be sort of "highlighted" in red, rather than the normal black. At least, that seems to be the intention.
However, I think I have seen cases where Codelite (or maybe gdb, idk) seems to sort of anticipate just prior to the change, e.g., when single stepping through code. It is also quite possible, eranif, that a bug in my own code may have corrupted either codelite's or gdb's idea of when the data was actually being modified (by me running MY code in Codelite). In fact, considering how many bugs in my own code I found early on, this is likely the reason, but I am not 100% certain of it.
I am not sure I can reproduce it now, but if I come across it again, I'll try to make a movie and post it here. A single still shot of the screen won't really illustrate the issue.
As an aside, though, could you or someone here confirm that the red highlighting is meant to draw user's attention to which variables have been updated? Again, from what I can tell by using Codelite, it seems that is the idea. Or maybe the intention is to tell the user an error has occurred, and places the variable name in red to signal this.