From 8fe23bc5200b7963deaa6ab89fa4a54b81f6fd47 Mon Sep 17 00:00:00 2001 From: Adrian McCarthy Date: Thu, 7 Sep 2017 18:29:48 +0000 Subject: Fix for bug 34510 - Minidump target does not resolve new symbols correctly Even though the content of the minidump does not change in a debugging session, frames can't be indiscriminately be cached since modules and symbols can be explicitly added after the minidump is loaded. The fix is simple, just let the base Thread::ClearStackFrames() do its job. submitted by amccarth on behalf of lemo Bug: https://bugs.llvm.org/show_bug.cgi?id=34510 Differential Revision: https://reviews.llvm.org/D37527 llvm-svn: 312735 --- lldb/source/Plugins/Process/minidump/ThreadMinidump.h | 2 -- 1 file changed, 2 deletions(-) (limited to 'lldb/source/Plugins/Process/minidump/ThreadMinidump.h') diff --git a/lldb/source/Plugins/Process/minidump/ThreadMinidump.h b/lldb/source/Plugins/Process/minidump/ThreadMinidump.h index 97db452edff..74ac44f74dc 100644 --- a/lldb/source/Plugins/Process/minidump/ThreadMinidump.h +++ b/lldb/source/Plugins/Process/minidump/ThreadMinidump.h @@ -37,8 +37,6 @@ public: lldb::RegisterContextSP CreateRegisterContextForFrame(StackFrame *frame) override; - void ClearStackFrames() override; - protected: lldb::RegisterContextSP m_thread_reg_ctx_sp; llvm::ArrayRef m_gpregset_data; -- cgit v1.2.3