Are you aware that a debugger cannot understand this C++ code which needs to be compiled?
I confess that I do not know all that can do a debugger or not, but I am aware at least of what it was doing before and what it is no longer able to do. ;-) And because I am an optimist guy, my motto is: "larger version, more features"...
Worse than the described issue, here is what I can do when I boot on my old partition of my mechanic hard drive designed in the last century (ubuntu 10.04):
Code:
...
entry *zone = ...; // here (1) , "entry" is a ldapcppei::class based on a "std::set" (cf. <http://homepage.gna.org/ldapcppei/>)
<breakpoint>
...
Watches give:
(*zone)["zoneName"]->getStrValue() = (display the actual str content of the attribute "zoneName") !...
(where "operator[](char*)" is a search method -and "attribute" positionning- of the class "entry" in libldapcppei ...)
Here I have to admit, like you, I become quite contemplative ... :shock: but: yes this works!... :shock: :shock:
(1): line 176 in <http://homepage.gna.org/ldapcppei/archives/ldapEasyAdminFrontends/sources/bind9domain.so/bind9domain.cpp>.
Complement: "tmp.toStdString()" (compiled) does not shock me. When "tmp" exists, its method "QString::toStdString()" simply points to the memory address of the "std::string" of the object. And, after all, the role of a debugger is to show the contents of memory addresses. (However, for the example above, I have no explanation for the fact that it works... I just see it works - with Lucid Lynx, not with my Oneric Ocelot and C::B 10.05...).
