From eb023e75dc9d0bbc0d88ba1379e449570b8678fa Mon Sep 17 00:00:00 2001 From: Greg Clayton Date: Fri, 11 Oct 2013 19:48:25 +0000 Subject: Added a way to set hardware breakpoints from the "breakpoint set" command with the new "--hardware" option. Hardware breakpoints are not a request, they currently are a requirement. So when breakpoints are specified as hardware breakpoints, they might fail to be set when they are able to be resolved and should be used sparingly. This is currently hooked up for GDB remote debugging. Linux and FreeBSD should quickly enable this feature if possible, or return an error for any breakpoints that are hardware breakpoint sites in the "virtual Error Process::EnableBreakpointSite (BreakpointSite *bp_site);" function. llvm-svn: 192491 --- lldb/source/Target/ThreadPlanRunToAddress.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lldb/source/Target/ThreadPlanRunToAddress.cpp') diff --git a/lldb/source/Target/ThreadPlanRunToAddress.cpp b/lldb/source/Target/ThreadPlanRunToAddress.cpp index 86825d2eb26..9e771397305 100644 --- a/lldb/source/Target/ThreadPlanRunToAddress.cpp +++ b/lldb/source/Target/ThreadPlanRunToAddress.cpp @@ -88,7 +88,7 @@ ThreadPlanRunToAddress::SetInitialBreakpoints () for (size_t i = 0; i < num_addresses; i++) { Breakpoint *breakpoint; - breakpoint = m_thread.CalculateTarget()->CreateBreakpoint (m_addresses[i], true).get(); + breakpoint = m_thread.CalculateTarget()->CreateBreakpoint (m_addresses[i], true, false).get(); if (breakpoint != NULL) { m_break_ids[i] = breakpoint->GetID(); -- cgit v1.2.3