Method DebugProcessView

core/processview.cpp:27–58

DebugProcessView::DebugProcessView(DebugNullView* nullView, BinaryView* parent):
	BinaryView("Debugger", parent->GetFile(), nullView)
{
	m_arch = parent->GetDefaultArchitecture();
	m_platform = parent->GetDefaultPlatform();
	m_addressSize = parent->GetAddressSize();
	auto bits = m_addressSize * 8;
	if (bits >= 64)
		m_length = UINT64_MAX;
	else
		m_length = (1ULL << bits) - 1;

	m_endian = parent->GetDefaultEndianness();

	// TODO: Read segments from debugger
	uint64_t length = PerformGetLength();
	// If we do not add any segments, BN will malfunction. If we add a binary view that is large, e.g., 0xffffffff,
	// it will be truncated to the size of the parent view. And the region from 0x0 to the size of the parent view will
	// be unreadable, because BN will try to read the byte values from the parent view, rather from the debug process
	// view, which eventually reads from the debug adapter backend. So, as a workaround, we add a segment that has size
	// 0x1, which minimizes the unreadable regions.
	// See https://github.com/Vector35/debugger/issues/334 for more details.
	AddAutoSegment(0, 1, 0, 1, SegmentReadable | SegmentWritable | SegmentExecutable);
	AddAutoSection("Memory", 0, length);

	m_aggressiveAnalysisUpdate = Settings::Instance()->Get<bool>("debugger.aggressiveAnalysisUpdate");

	m_controller = DebuggerController::GetController(parent);
	m_eventCallback = m_controller->RegisterEventCallback([this](const DebuggerEvent& event){
		eventHandler(event);
	}, "Process View");
}


DebugProcessView::~DebugProcessView()