[llvm-dev] UBSan runtime options

[Romanova, Katya via llvm-dev]

Excellent!
Thank you, Kostya.

Katya.

From: Kostya Serebryany [mailto:kcc at google.com]
Sent: Thursday, November 19, 2015 6:15 PM
To: Romanova, Katya
Cc: llvm-dev at lists.llvm.org; Alexey Samsonov
Subject: Re: UBSan runtime options



On Thu, Nov 19, 2015 at 4:14 PM, Romanova, Katya <Katya_Romanova at playstation.sony.com<mailto:Katya_Romanova at playstation.sony.com>> wrote:

Hello,

I 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?

UBSAN_OPTIONS=log_path=YOUR_FILE

(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?
the other allowed value is 0, and this is just a common syntax for all the flags.
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?

We hope to have clang.llvm.org/docs/UndefinedBehaviorSanitizer.html<http://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html> or some such in at most ~2 weeks (yes, this is long overdue, sorry).


This one is pretty good, but it doesn't talk about many things. E.g. it doesn't describe the runtime options that are possible to pass to UBSan (like the one that I talked about earlier).
http://clang.llvm.org/docs/UsersManual.html
This page below doesn't seems to mention UBSan at all (unlike the others most commonly used sanitizers). Is it done on purpose? Or it’s a work in progress?
http://clang.llvm.org/docs/

Thanks, Katya.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151120/1f97d5d6/attachment.html>