<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1">My simplified test case file only contains one
function, with others commented out.<br>
</font></p>
<p><font size="+1">I tried the RelWithDebInfo CMake build type, it
slightly reduced the time to reach the first breakpoint from 21
to 16 seconds when I ran it with lldb command line. But when I
debug clang in vscode, this configuration doesn't stop at the
breakpoint (with the CodeLLDB extension). The Debug build stops
at the breakpoint. Saving 4 seconds on command line is not
useful because setting or canceling a breakpoint on the command
line takes more time for me in the unfamiliar code base.</font></p>
<p><font size="+1">I already used gdb-add-index to the clang
executable file.<br>
</font></p>
<p><font size="+1">Any other method might help?<br>
</font></p>
<p><font size="+1">How much time does it take you to stop at a
breakpoint in a checker?<br>
</font></p>
<pre class="moz-signature" cols="72">Love,
Lou
</pre>
<div class="moz-cite-prefix">On 09/28/2018 02:27 PM, George
Karpenkov wrote:<br>
</div>
<blockquote type="cite"
cite="mid:D777A81D-03C0-436E-8EA1-89EE3CF479C1@apple.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
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><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="" moz-do-not-send="true">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 class="" size="+1">Hi,</font></p>
<p class=""><font class="" size="+1">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
class="" size="+1">function when I run the following
command:</font></p>
<pre class=""><font class="" size="+1">lldb-6.0 -- clang-8 -cc1 -analyze -analyzer-checker=alpha.unix.SimpleStream \
test/Analysis/simple-stream-checks.c</font></pre>
<p class=""><font class="" size="+1">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=""
moz-do-not-send="true">cfe-dev@lists.llvm.org</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</blockquote>
<br>
</body>
</html>