[Lldb-commits] [PATCH] D15834: Handle hardcoded breakpoints on Windows (e.g., int3 or __debugbreak())

Zachary Turner via lldb-commits lldb-commits at lists.llvm.org
Wed Dec 30 18:35:17 PST 2015

zturner added inline comments.

Comment at: source/Plugins/Process/Windows/Live/ProcessWindowsLive.cpp:601-605
@@ -579,5 +600,7 @@
+                // The thread hit a hard-coded breakpoint like an `int 3` or `__debugbreak()`.
-                             "Breakpoint site %d is not valid for this thread, creating empty stop info.",
-                             site->GetID());
+                                "No breakpoint site matches for this thread. __debugbreak()?  "
+                                "Creating stop info with the exception.");
+                // FALLTHROUGH:  We'll treat this as a generic exception record in the default case.
When you do a disassembly, does the arrow point to the int 3 or to the instruction after the int 3?

Also what does the output look like when you do a backtrace?


More information about the lldb-commits mailing list