[Bug mi/16213] New: -var-update still keeps "var1.<error at 0>"

["jan.kratochvil at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16213

            Bug ID: 16213
           Summary: -var-update still keeps "var1.<error at 0>"
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
          Assignee: unassigned at sourceware dot org
          Reporter: jan.kratochvil at redhat dot com
            Target: x86_64-unknown-linux-gnu

Eclipse fails to print local std::set variable.  I believe it is a GDB MI bug.

FAIL: gdb-7.6.1-46.fc19.x86_64
FAIL: GNU gdb (GDB) 7.6.50.20131124-cvs

Why GDB still insists on "var1.<error at 0>" even after -var-update?
Removing earlier
  32-var-list-children var1
fixes the problem, it then prints:
 
99^done,numchild="1",children=[child={name="var1.[0]",exp="[0]",numchild="1",type="C",thread-id="1"}],has_more="0"

------------------------------------------------------------------------------
#include <set>
class C {
public:
  int i;
  C(int *ip):i(*ip) {}
};
namespace std {
  template<> bool less<C>::operator()(const C &a,const C &b) const { return
a.i<b.i; }
}
int main() {
  int i=1;
  std::set<C> xxxvariable;
  xxxvariable.insert(C(&i));
  return 0;
}
------------------------------------------------------------------------------
gdb -i=mi <cmd
------------------------------------------------------------------------------
5-enable-pretty-printing
15-file-exec-and-symbols ./cxx
18-break-insert -t -f main
20-exec-run
31-var-create --thread 1 --frame 0 - * xxxvariable
32-var-list-children var1
33-break-insert -t -f cxx.cpp:14
34-exec-continue
38-var-update var1
99-var-list-children var1
------------------------------------------------------------------------------
38^done,changelist=[]
99^done,numchild="1",children=[child={name="var1.<error at 0>",exp="<error at
0>",numchild="36",type="char [36]",thread-id="1"}],has_more="0"

-- 
You are receiving this mail because:
You are on the CC list for the bug.