> The blurb you wrote in the changelog: > > | The libbfd C++ demangler doesn't seem to deal with cloned functions, > | like symbol.clone.NUM. > | > | Just strip the dot part before demangling and add it back later. > > Only alludes to a C++ symbol resolution annoyance and thus isn't very > informative.
The issue was that I saw a long unreadable line noise string in report/top, instead of a demangled function. After I stripped the postfix I got the demangled symbol as expected. -Andi -- a...@linux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
