Displaying 3 results from an estimated 3 matches for "__lsan_disable".
2014 Jan 09
2
[LLVMdev] [cfe-dev] lsan for LLVM bootstrap; leaks in TableGen
...rned_off is explained in
> +// compiler-rt/include/sanitizer/lsan_interface.h
> +int __lsan_is_turned_off() { return 1; }
> +} // extern “C"
[ Sorry to be joining the conversation late ]
What is the reasoning behind having them define a function to disable lsan, rather than calling __lsan_disable?
Is it so that lsan can be turned off before main() is entered?
I’m not really happy with the idea of the user having to define a function with a reserved name in their code.
— Marshall
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipe...
2013 Dec 26
3
[LLVMdev] [cfe-dev] lsan for LLVM bootstrap; leaks in TableGen
On Thu, Dec 26, 2013 at 2:40 AM, Kostya Serebryany <kcc at google.com> wrote:
> Like this?
>
> +extern "C" {
> +// Disable LeakSanitizer, see http://llvm.org/bugs/show_bug.cgi?id=18325.
>
We don't often reference bugs in comments. I would give a brief summary in
the text of the comment, and mention the bug in the commit log.
-------------- next part
2015 Nov 10
2
Docs for leak checker (and other sanitizers)?
On Mon, Nov 9, 2015 at 7:20 PM, Kostya Serebryany <kcc at google.com> wrote:
> Most likely, you need
> https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSanitizer
Thanks!
> I don't think lsan supports this mode directly,
> but why do you think that the init-time allocations are going to be
> "leaked"?
> If there is some object still pointing to