From 4eacc7647d7c043fdbfbe621e4c4f3c1c202d979 Mon Sep 17 00:00:00 2001 From: Jason Molenda Date: Sat, 26 Jan 2013 05:30:38 +0000 Subject: [PATCH] Add comments showing the symbolic names for the exc_code types we receive with an EXC_BREAKPOINT mach exception on arm. llvm-svn: 173560 --- lldb/source/Plugins/Process/Utility/StopInfoMachException.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lldb/source/Plugins/Process/Utility/StopInfoMachException.cpp b/lldb/source/Plugins/Process/Utility/StopInfoMachException.cpp index 60570b5..77bc711 100644 --- a/lldb/source/Plugins/Process/Utility/StopInfoMachException.cpp +++ b/lldb/source/Plugins/Process/Utility/StopInfoMachException.cpp @@ -389,7 +389,7 @@ StopInfoMachException::CreateStopReasonWithMachException break; case llvm::Triple::arm: - if (exc_code == 0x102) + if (exc_code == 0x102) // EXC_ARM_DA_DEBUG { // It's a watchpoint, then, if the exc_sub_code indicates a known/enabled // data break address from our watchpoint list. @@ -408,7 +408,7 @@ StopInfoMachException::CreateStopReasonWithMachException if (thread.GetTemporaryResumeState() == eStateStepping) return StopInfo::CreateStopReasonToTrace(thread); } - else if (exc_code == 1) + else if (exc_code == 1) // EXC_ARM_BREAKPOINT { is_software_breakpoint = true; is_trace_if_software_breakpoint_missing = true; -- 2.7.4