https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #7 from Mark Wielaard <m...@klomp.org> --- v3 does work. But I admit to not fully understand why/how. The addr_load_di calls in coregrind/m_stacktrace..c seems unnecessary (you can comment them out and things still work fine). This is because there is a addr_load_di call in describe_IP and find_DiCfSI. Which makes sense since those methods are called when the debuginfo for an executable address are consulted. I do wonder if addr_load_di can be made a bit cheaper. Currently it does a search for the DebugInfo by calling find_DebugInfo which goes over the debugInfo_list. find_DiCfSI does something similar. And describe_IP is called with a InlIPCursor which already is associated with a particular DebugInfo. I couldn't immediately find a way to "load" those DebugInfos instead of calling addr_load_di, so maybe the "double" search is necessary. -- You are receiving this mail because: You are watching all bug changes.
