🚀 go-pugleaf

Hi all.

I'm hope this is right group.

I'm working with GDB/MI. I'm stepping on C++ code (actually it is 
SystemC code). I want to read local variable 'VALIDATED' of current frame:

-var-create - * VALIDATED
^done,name="var2",numchild="0",type="int"
-var-info-type var2
^done,type="int"
-var-update var2
^done,changelist=[{name="var2",in_scope="false"}]
-var-evaluate-expression var2
^done,value="77828156"
-var-delete var2
^done,ndeleted="1"

As you can see there is garbage instead of real variable value.

However if I do exactly the same instructions again (no change in 
debugger between) I get proper value:

-var-create - * VALIDATED
^done,name="var3",numchild="0",type="int"
-var-info-type var3
^done,type="int"
-var-update var3
^done,changelist=[]
-var-evaluate-expression var3
^done,value="1"
-var-delete var3
^done,ndeleted="1"

I cannot support You with this piece of code. But anyway problem exists 
_every_ time, first "evaluate-expression" always returns garbage. I mean 
"first" after any step instruction. This happens with all "numeric" 
variables in my code. Looks like GDB/MI bug for me.

GDB 6.3/windows.

Sebastian Bialy.