Displaying 2 results from an estimated 2 matches for "ubsan_diag".
2014 Oct 06
3
[LLVMdev] [PATCH] ubsan: label messages as coming from ubsan
...ble
as well. It would also be nice if there were a blurb on what the error
was rather than just freeform text (similar to heap-use-after-free and
heap-buffer-overflow) to categorize messages.
Thanks,
--Ben
Ben Boeckel (1):
ubsan: add 'UndefinedBehaviorSanitizer' to messages
lib/ubsan/ubsan_diag.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.1.0
2014 Oct 09
4
[LLVMdev] Remaining Compiler-RT failures in ARM
...es/Misc/missing_return.cpp:6:5:
runtime error: execution reached the end of a value-returning function
without returning a value
#0 0x1c7cf in f()
.../compiler-rt/test/ubsan/TestCases/Misc/missing_return.cpp:6:9
#1 0x195cf in __ubsan::ScopedReport::~ScopedReport()
.../compiler-rt/lib/ubsan/ubsan_diag.cc:341
#2 0x1ae79 in handleMissingReturnImpl(__ubsan::UnreachableData*,
__ubsan::ReportOptions) [clone .constprop.7]
.../compiler-rt/lib/ubsan/ubsan_handlers.cc:254
#3 0x1b31f in __ubsan_handle_missing_return
.../compiler-rt/lib/ubsan/ubsan_handlers.cc:259
Maybe the stack is not deep enoug...