aboutsummaryrefslogtreecommitdiff
path: root/src/third_party/libdisasm/x86_disasm.c
diff options
context:
space:
mode:
authorvapier@chromium.org <vapier@chromium.org@4c0a9323-5329-0410-9bdc-e9ce6186880e>2013-12-11 05:38:34 +0000
committervapier@chromium.org <vapier@chromium.org@4c0a9323-5329-0410-9bdc-e9ce6186880e>2013-12-11 05:38:34 +0000
commit4c048c97644b0cbc77d6f982afdc7b04928ac65d (patch)
tree3b84ead6474c8174a4ac37a4662c7bf4a320a546 /src/third_party/libdisasm/x86_disasm.c
parentAddress additional comments from r1248. Fix the register to check and fix som... (diff)
downloadbreakpad-4c048c97644b0cbc77d6f982afdc7b04928ac65d.tar.xz
disable unittests under ASAN that use memory crashes
There are a bunch of tests that use invalid memory acesses (on purpose) to trigger a crash so that we can detect things are dumped correctly. When we run under ASAN, it catches those accesses and the breaks the testing flow. For now, use the existing ADDRESS_SANITIZER symbol to disable more tests. Ideally we'd use a compile-time attribute to disable ASAN on a few funcs, but that seems to be broken atm. BUG=chromium:293519 BUG=chromium:304575 TEST=ran unittests under ASAN and they now pass TEST=ran unittests w/out asan/clang and they still pass R=benchan@chromium.org Review URL: https://breakpad.appspot.com/884002 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1255 4c0a9323-5329-0410-9bdc-e9ce6186880e
Diffstat (limited to 'src/third_party/libdisasm/x86_disasm.c')
0 files changed, 0 insertions, 0 deletions