|
From: Dennis L. <pla...@gm...> - 2004-10-13 21:04:09
|
Hi people,
Im using valgrind from cvs, and noticed that in a few cases, something from
C++ is not demangled by valgrind. Do I need to tell valgrind something else
? Most things are demangled correctly.
Im using gcc 3.3.3 on a SuSE machine.
This is the output by valgrind :
by 0x1B96B3D7:
_ZNSt8_Rb_treeIPKcSt4pairIKS1_SsESt10_Select1stIS4_EN5iwear12cstring_lessESaIS4_EE12insert_equalISt17_Rb_tree_iteratorIS4_RS4_PS4_EEEvT_SG_
(stl_tree.h:1150)
by 0x1B96A3A8:
_ZNSt8multimapIPKcSsN5iwear12cstring_lessESaISt4pairIKS1_SsEEE6insertISt17_Rb_tree_iteratorIS6_RS6_PS6_EEEvT_SE_
(stl_multimap.h:363)
The multimap there is declared as following :
multimap<const char *, string, iwear::cstring_less>
while the insert operation done on it is this :
its insert(iterator,iterator) function
Another not demangled name is :
by 0x1B986722: _GLOBAL__I__ZN5iwear3uid6wehaveE (stl_set.h:100)
which is declared as following :
class uid
{
static set<iwear::uid*,deref_less<iwear::uid*> > wehave;
}
any hints ?
greets
Dennis
Carpe quod tibi datum est
|