llvm dev - Mar 2011 - [LLVMdev] static analyzer & ubigraph visualization

I updated our project recently to use a newer version of clang (we're at
r127188 now).  That version made our modified ccc-analyze script stop working,
so updated that from TOT clang as well.  I noticed in the new script a new
environment variable check "CCC_UBI" that uses Ubigraph to visualize
something... but what?  I tried making a simple project with a few kinds of
static analyzer errors, but nothing ever shows up in my ubigraph window. 
What's this feature for and what should I see graphed?

-- Carl

Hi Carl,

For future reference, the correct list for questions on the analyzer is cfe-dev,
not llvmdev.

CCC_UBI is meant to display the analysis path graph (aka "exploded
graph") as it gets explored by the analyzer.  I haven't run it in a
while, so it may be broken.  I will investigate.

Ted

On Mar 8, 2011, at 11:12 AM, Carl Norum wrote:
> I updated our project recently to use a newer version of clang (we're
at r127188 now).  That version made our modified ccc-analyze script stop
working, so updated that from TOT clang as well.  I noticed in the new script a
new environment variable check "CCC_UBI" that uses Ubigraph to
visualize something... but what?  I tried making a simple project with a few
kinds of static analyzer errors, but nothing ever shows up in my ubigraph
window.  What's this feature for and what should I see graphed?
> 
> -- Carl
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Hi Carl,

I think the trick is to use a debug build of Clang.  The ubigraph support is not
enabled in a release build as it is in a hot path of the analyzer.  I switched
to using a debug build and the ubigraph support worked for me.  You also need
the 'ubiviz' script in your path.

Ted

On Mar 8, 2011, at 11:26 AM, Ted Kremenek wrote:
> Hi Carl,
> 
> For future reference, the correct list for questions on the analyzer is
cfe-dev, not llvmdev.
> 
> CCC_UBI is meant to display the analysis path graph (aka "exploded
graph") as it gets explored by the analyzer.  I haven't run it in a
while, so it may be broken.  I will investigate.
> 
> Ted
> 
> On Mar 8, 2011, at 11:12 AM, Carl Norum wrote:
> 
>> I updated our project recently to use a newer version of clang
(we're at r127188 now).  That version made our modified ccc-analyze script
stop working, so updated that from TOT clang as well.  I noticed in the new
script a new environment variable check "CCC_UBI" that uses Ubigraph
to visualize something... but what?  I tried making a simple project with a few
kinds of static analyzer errors, but nothing ever shows up in my ubigraph
window.  What's this feature for and what should I see graphed?
>> 
>> -- Carl
>> 
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> 
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev