steleman / address-sanitizer

Automatically exported from code.google.com/p/address-sanitizer
0 stars 0 forks source link

ASan with online symbolizer sometimes produces mangled function names #335

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
In Chromium:

$ git pull 67fa5e94bdbd9eb7bce39c0cd6922321cf4998c9 && gclient sync
$ GYP_GENERATORS=ninja GYP_DEFINES="asan=1 lsan=1" gclient runhooks && ninja 
dbus_unittests
$ ASAN_OPTIONS=symbolize=1:detect_leaks=1 out/Release/dbus_unittests 
--gtest_filter=ObjectManagerTest.RemoveSecondObject 2>&1 | grep 
_ZN4base4BindIMN4dbus17ObjectMa

    #1 0x583b2a in _ZN4base4BindIMN4dbus17ObjectManagerTestEFvRKNS1_10ObjectPathERKNSt3__112basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEEENS_8internal17UnretainedWrapperIS2_EES3_EENS_8CallbackINSH_9BindStateINSH_13FunctorTraitsIT_E12RunnableTypeENSO_7RunTypeEFvNSH_19CallbackParamTraitsIT0_Xsr14IsMoveOnlyTypeISS_EE5valueEE11StorageTypeENSR_IT1_Xsr14IsMoveOnlyTypeISV_EE5valueEE11StorageTypeEEE14UnboundRunTypeEEESN_RKSS_RKSV_ base/bind.h:168:3
    #7 0x583c8c in _ZN4base4BindIMN4dbus17ObjectManagerTestEFvRKNS1_10ObjectPathERKNSt3__112basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEEENS_8internal17UnretainedWrapperIS2_EES3_EENS_8CallbackINSH_9BindStateINSH_13FunctorTraitsIT_E12RunnableTypeENSO_7RunTypeEFvNSH_19CallbackParamTraitsIT0_Xsr14IsMoveOnlyTypeISS_EE5valueEE11StorageTypeENSR_IT1_Xsr14IsMoveOnlyTypeISV_EE5valueEE11StorageTypeEEE14UnboundRunTypeEEESN_RKSS_RKSV_ base/bind.h:168

Original issue reported on code.google.com by earth...@google.com on 29 Aug 2014 at 8:04

GoogleCodeExporter commented 9 years ago
Is this a properly mangled name? When I run c++filt on it, it is unable to do 
the demangling.

Original comment by samso...@google.com on 29 Aug 2014 at 8:27

GoogleCodeExporter commented 9 years ago
I have no idea.

Original comment by earth...@chromium.org on 29 Aug 2014 at 8:29

GoogleCodeExporter commented 9 years ago
Can you try to obtain the same stack trace from smth. like gdb and see if it's 
properly demangled there?

Original comment by samso...@google.com on 29 Aug 2014 at 8:46

GoogleCodeExporter commented 9 years ago
Yes, this is what I see in GDB:

#1  0x0000000000587d47 in Bind<void 
(dbus::ObjectManagerTest::*)(dbus::ObjectPath const&, 
std::__1::basic_string<char, std::__1::char_traits<char>, 
std::__1::allocator<char> > const&), 
base::internal::UnretainedWrapper<dbus::ObjectManagerTest>, dbus::ObjectPath> 
() at ../../dbus/object_path.h:37

Original comment by earth...@chromium.org on 1 Sep 2014 at 11:35