Displaying 2 results from an estimated 2 matches for "print_stacktrac".
Did you mean:
print_stacktrace
2015 Nov 20
2
UBSan runtime options
...have several low priority UBSan questions...
(1) Is there a way for UBSan to print its output to a file that the user specified (e.g. via option) instead of dumping everything on stderr?
(2) Out of curiosity, why is the name of the option for printing the stacktrace spelled
"UBSAN_OPTIONS=print_stacktrace=1", though the allowed value is 1?
Since the only one value is accepted, maybe it's more practical (and intuitive) to spell it
"UBSAN_OPTIONS=print_stacktrace"
(4) Do you know if there is better (i.e. more complete) documentation for UBSan somewhere?
This one is pretty good,...
2014 Oct 09
4
[LLVMdev] Remaining Compiler-RT failures in ARM
...nitizer mode,
making it impossible to mark it as XFAIL. Before making XFAIL more
powerful, I'd rather find the problem and try to solve it.
The file checks for two copies of missing_return.cpp, one for f() and
one for main(), but on ARM's stack trace, there's only one:
$ UBSAN_OPTIONS=print_stacktrace=1 ./missing_return.cpp.tmp
.../compiler-rt/test/ubsan/TestCases/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 __...