<div dir="ltr">I assumed that the leak is in libedit code, which we can't fix.<div><br></div><div>It's possible (though less likely) that libedit passes the result of wstrdup back to the caller and expects us to deallocate it.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 15, 2015 at 1:31 AM, Kostya Serebryany <span dir="ltr"><<a href="mailto:kcc@google.com" target="_blank">kcc@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would say, run with <span style="font-size:13px">ASAN_OPTIONS=fast_unwind_on_</span><span style="font-size:13px">malloc=0 and let us see the stack trace. </span><div><span style="font-size:13px">We are not using the suppressions with llvm yet,</span></div><div><span style="font-size:13px">and we are not yet using </span><span style="font-size:13px">ScopedDisabler in the LLVM sources. </span></div><div><span style="font-size:13px">If this is an intentional leak that happens once in the process we have BuryPointer for that. </span></div><div><span style="font-size:13px">If this is a real bad leak, use </span><span style="font-size:13px">ScopedDisabler locally, but don't commit (fix instead). </span></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 14, 2015 at 6:39 AM, Sergey Matveev <span dir="ltr"><<a href="mailto:earthdok@google.com" target="_blank">earthdok@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Run it with the slow unwinder (ASAN_OPTIONS=fast_unwind_on_malloc=0) to identify the call site, then wrap the call in an __lsan::ScopedDisabler.<div><br></div><div>- Sergey</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Wed, Jan 14, 2015 at 1:27 PM, Chandler Carruth <span dir="ltr"><<a href="mailto:chandlerc@google.com" target="_blank">chandlerc@google.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">I get leaks from a system library:<div><br></div><div><div>==16272==ERROR: LeakSanitizer: detected memory leaks</div><div><br></div><div>Direct leak of 148 byte(s) in 2 object(s) allocated from:</div><div> #0 0x4a3172 in __interceptor_malloc .../build/../projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3</div><div> #1 0x7f575d8df1fe in wcsdup (/lib64/libedit.so.0+0x1c1fe)</div></div><div><br></div><div>I don't think I can fix this... ;]</div><span><font color="#888888"><div><br></div><div>-Chandler</div></font></span></div>
<br></div></div>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>