From cbee13e04c9f7070681a66cc2d26faa86927d83c Mon Sep 17 00:00:00 2001 From: Timur Iskhodzhanov Date: Mon, 2 Jun 2014 13:40:41 +0000 Subject: [Sanitizer/interception Win] Break into the debugger on unknown instructions llvm-svn: 210028 --- compiler-rt/lib/interception/interception_win.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'compiler-rt/lib') diff --git a/compiler-rt/lib/interception/interception_win.cc b/compiler-rt/lib/interception/interception_win.cc index fe47b627cc0..9eabe52eb90 100644 --- a/compiler-rt/lib/interception/interception_win.cc +++ b/compiler-rt/lib/interception/interception_win.cc @@ -134,8 +134,9 @@ static size_t RoundUpToInstrBoundary(size_t size, char *code) { // FIXME: Unknown instruction failures might happen when we add a new // interceptor or a new compiler version. In either case, they should result // in visible and readable error messages. However, merely calling abort() - // or __debugbreak() leads to an infinite recursion in CheckFailed. + // leads to an infinite recursion in CheckFailed. // Do we have a good way to abort with an error message here? + __debugbreak(); return 0; } -- cgit v1.2.3