Adrian McCarthy 8fe23bc520 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
2017-09-07 18:29:48 +00:00

51 lines
1.2 KiB
C++

//===-- ThreadMinidump.h ---------------------------------------*- C++ -*-===//
//
// The LLVM Compiler Infrastructure
//
// This file is distributed under the University of Illinois Open Source
// License. See LICENSE.TXT for details.
//
//===----------------------------------------------------------------------===//
#ifndef liblldb_ThreadMinidump_h_
#define liblldb_ThreadMinidump_h_
// Project includes
#include "MinidumpTypes.h"
// Other libraries and framework includes
#include "lldb/Target/Thread.h"
// C Includes
// C++ Includes
namespace lldb_private {
namespace minidump {
class ThreadMinidump : public Thread {
public:
ThreadMinidump(Process &process, const MinidumpThread &td,
llvm::ArrayRef<uint8_t> gpregset_data);
~ThreadMinidump() override;
void RefreshStateAfterStop() override;
lldb::RegisterContextSP GetRegisterContext() override;
lldb::RegisterContextSP
CreateRegisterContextForFrame(StackFrame *frame) override;
protected:
lldb::RegisterContextSP m_thread_reg_ctx_sp;
llvm::ArrayRef<uint8_t> m_gpregset_data;
bool CalculateStopInfo() override;
};
} // namespace minidump
} // namespace lldb_private
#endif // liblldb_ThreadMinidump_h_