|
From: Tom H. <to...@co...> - 2005-05-17 10:42:05
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
> On Tuesday 17 May 2005 03:59, Nicholas Nethercote wrote:
>> On Mon, 16 May 2005, Dennis Lubert wrote:
>> > with valgrind 2.4 svn rev 414744 I have a problem with sometimes symbols
>> > not demangled. In one case it lloks just like a usual longer symbol :
>> >
>> > _ZNSt8_Rb_treeIPKcSt4pairIKS1_N5iwear14iwear_languageEESt10_Select1stIS6_
>> >ENS4_12cstring_lessESaIS6_EEC1ERKS9_RKSA_ (stl_tree.h:730)
>> >
>> > while in the other case it has some _GLOBAL prefix :
>> >
>> > _GLOBAL__I__ZN5iwear4i18n17locale_code_tableE (stl_map.h:120)
>> >
>> > is there any trick to get valgrind to demangling these symbols too ?
>>
>> Does increasing M_VG_ERRTXT help? Probably not, but I can't think of
>> anything else.
>
> Valgrind just uses the standard GNU C++ demangler (c++filt) code.
> So first thing to try is to see if c++filt can make sense of
> either of these symbols (it can't).
My one can sort of handle the second one:
dellow [~] % c++filt
_GLOBAL__I__ZN5iwear4i18n17locale_code_tableE
global constructors keyed to _ZN5iwear4i18n17locale_code_tableE
Of course valgrind's copy of the demangler is fairly old now so we
might need to update it at some point.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|