aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTimur Iskhodzhanov <timurrrr@google.com>2014-06-02 13:40:41 +0000
committerTimur Iskhodzhanov <timurrrr@google.com>2014-06-02 13:40:41 +0000
commitcbee13e04c9f7070681a66cc2d26faa86927d83c (patch)
treef2a5e923b6bacded9e055e8cea5f1e8fb483366b
parent51fadc387a6bbd9b9b6cb5adfb7c170110ecc154 (diff)
downloadllvm-cbee13e04c9f7070681a66cc2d26faa86927d83c.zip
llvm-cbee13e04c9f7070681a66cc2d26faa86927d83c.tar.gz
llvm-cbee13e04c9f7070681a66cc2d26faa86927d83c.tar.bz2
[Sanitizer/interception Win] Break into the debugger on unknown instructions
llvm-svn: 210028
-rw-r--r--compiler-rt/lib/interception/interception_win.cc3
1 files changed, 2 insertions, 1 deletions
diff --git a/compiler-rt/lib/interception/interception_win.cc b/compiler-rt/lib/interception/interception_win.cc
index fe47b62..9eabe52 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;
}