<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Lou,<div class=""><br class=""></div><div class="">Somehow I haven’t seen your follow up email.</div><div class="">Can you describe a full reproducible example?</div><div class="">With an exact command line invocation, exact input file, and exact breakpoint line.</div><div class=""><br class=""></div><div class="">George</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 28, 2018, at 2:27 PM, George Karpenkov via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Lou,<div class=""><br class=""></div><div class="">You probably want to only debug the analysis running on a function you are interested in.</div><div class="">-Xclang -analyzer-display-progress</div><div class="">shows what functions the analyzer is going through, and</div><div class="">-Xclang -analyze-function “function-name”</div><div class="">let’s you select the function (use the exact name copied from the previous list).</div><div class=""><br class=""></div><div class="">You can also try release+debuginfo configuration if the former is too slow.</div><div class="">20 seconds does sound excessive for a simple test file in any case though, so that is strange.<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Sep 28, 2018, at 1:49 PM, Lou Wynn via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class=""><font size="+1" class="">Hi,</font></p><p class=""><font size="+1" class="">I'm now having a question of how to speed up
startup runs of a static analysis checker in the lldb debugger.
It takes about 21 seconds for the debugger to stop at the first
breakpoint at the SimpleStreamChecker::checkPreCall </font><font size="+1" class="">function when I run the following command:</font></p>
<pre class=""><font size="+1" class="">lldb-6.0 -- clang-8 -cc1 -analyze -analyzer-checker=alpha.unix.SimpleStream \
test/Analysis/simple-stream-checks.c</font></pre><p class=""><font size="+1" class="">Are there ways to make it faster? I run many debugging
sessions not only to figure out how the static analyzer works
but also to debug my first checker. Any time saving method is
appreciated.<br class="">
</font></p>
<pre class="moz-signature" cols="72">--
Love,
Lou
</pre>
</div>
_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev<br class=""></div></blockquote></div><br class=""></div></body></html>