<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 19, 2014, at 4:40 AM, Evgeniy Stepanov <<a href="mailto:eugeni.stepanov@gmail.com" class="">eugeni.stepanov@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">It looks like r219010 or one of the related commits may be the cause<br class="">of this memory leak:<br class=""><a href="http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/5116/steps/check-clang asan/logs/stdio" class="">http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/builds/5116/steps/check-clang%20asan/logs/stdio</a><br class=""></div></blockquote><div><br class=""></div><div>This looks related to the debug info for forward declarations that I finished committing a couple of days ago. I don’t think it is related to Duncan’s work. I’ll take a look.</div><div><br class=""></div><div>Fred</div><br class=""><blockquote type="cite" class=""><div class="">The bot was down for a long time, so we don't have a better<br class="">indication, and ownership of MDNode objects is a bit unclear in this<br class="">code. Could you take a look please?<br class=""><br class=""><br class="">On Sat, Oct 4, 2014 at 7:20 PM, Duncan P. N. Exon Smith<br class=""><<a href="mailto:dexonsmith@apple.com" class="">dexonsmith@apple.com</a>> wrote:<br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class="">On 2014 Oct 3, at 17:37, Adrian Prantl <<a href="mailto:aprantl@apple.com" class="">aprantl@apple.com</a>> wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Oct 3, 2014, at 5:34 PM, Duncan P. N. Exon Smith <<a href="mailto:dexonsmith@apple.com" class="">dexonsmith@apple.com</a>> wrote:<br class=""><br class="">Oops!  Updating that document was faster than I expected.  This must<br class="">be why.<br class=""><br class="">Looking more closely, the examples don't seem better than looking<br class="">directly at `include/llvm/IR/DebugInfo.h` and `lib/IR/DIBuilder.cpp`.<br class=""><br class="">In the attached patch, I update a few of them, but prune the rest, and<br class="">point the reader at the appropriate place in the source.<br class=""><br class="">Thoughts?<br class=""></blockquote><br class="">Looks like you found a way to reduce the maintenance effort while increasing the accuracy of the documentation. I won’t complain :-)<br class=""></blockquote><br class="">r219051<br class="">_______________________________________________<br class="">llvm-commits mailing list<br class=""><a href="mailto:llvm-commits@cs.uiuc.edu" class="">llvm-commits@cs.uiuc.edu</a><br class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits<br class=""></blockquote><br class="">_______________________________________________<br class="">llvm-commits mailing list<br class=""><a href="mailto:llvm-commits@cs.uiuc.edu" class="">llvm-commits@cs.uiuc.edu</a><br class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits<br class=""></div></blockquote></div><br class=""></body></html>