summaryrefslogtreecommitdiff
path: root/Kernel/VM/MemoryManager.cpp
diff options
context:
space:
mode:
authorAndreas Kling <kling@serenityos.org>2021-03-30 11:49:35 +0200
committerAndreas Kling <kling@serenityos.org>2021-03-30 11:50:49 +0200
commit54f6b52f713d996999bd718b71f7e378fcc01bb1 (patch)
treed6ce8dbf6f0e21de33f6c0fb5fe49de5c7cfa8c0 /Kernel/VM/MemoryManager.cpp
parent664571c88fe03f65971fc1bcaa5086f6c431e60e (diff)
downloadserenity-54f6b52f713d996999bd718b71f7e378fcc01bb1.zip
Kernel: Don't dump regions twice when crashing due to bad access
For whatever reason we were dumping regions when first handling the page fault, and then again when tearing down the process.
Diffstat (limited to 'Kernel/VM/MemoryManager.cpp')
-rw-r--r--Kernel/VM/MemoryManager.cpp1
1 files changed, 0 insertions, 1 deletions
diff --git a/Kernel/VM/MemoryManager.cpp b/Kernel/VM/MemoryManager.cpp
index c264c81a8c..02cd252d45 100644
--- a/Kernel/VM/MemoryManager.cpp
+++ b/Kernel/VM/MemoryManager.cpp
@@ -475,7 +475,6 @@ PageFaultResponse MemoryManager::handle_page_fault(const PageFault& fault)
dbgln_if(PAGE_FAULT_DEBUG, "MM: CPU[{}] handle_page_fault({:#04x}) at {}", Processor::id(), fault.code(), fault.vaddr());
auto* region = find_region_from_vaddr(fault.vaddr());
if (!region) {
- Process::current()->space().dump_regions();
return PageFaultResponse::ShouldCrash;
}