<br><br>
<div class="gmail_quote">On Tue, May 12, 2009 at 5:47 PM, Bill Wendling <span dir="ltr"><<a href="mailto:isanbard@gmail.com">isanbard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">On Tue, May 12, 2009 at 5:03 PM, Mark A. Lyan <<a href="mailto:omineo@gmail.com">omineo@gmail.com</a>> wrote:<br>> Gurus-<br>><br>> Do llvm-gcc or clang provide a way to catch use-after-free types of issues?<br>
><br></div>llvm-gcc and clang don't. But I believe that the static analyzer has<br>facilities for this.<br><br> <a href="http://clang.llvm.org/StaticAnalysis.html" target="_blank">http://clang.llvm.org/StaticAnalysis.html</a></blockquote>

<div> </div>
<div>Ah! I will investigate this further. Thanks for the help.</div>
<div> </div>
<div>-KC</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span id=""></span><br>-bw<br><br>_______________________________________________<br>LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">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>
</blockquote></div><br>