[cfe-dev] Static analysis and Adium
toddransom at mac.com
Mon Jul 7 08:39:11 PDT 2008
No, I was talking about the table produced by the scan-build command
line interface. I see now that it is sortable. It might be nice to
provide some visual indicator of that. The default table sort seems to
be by bug type. If you added a sort indicator to that column by
default it would be more obvious the table is sortable.
StoryMill & Montage Development
On Jul 7, 2008, at 11:32 AM, Ted Kremenek wrote:
> Hi Todd,
> BTW, after I sent my last email, I realized that you may have been
> referring to the table on the Adium wiki:
> This table was not produced by the static analysis tool.
> The tool itself produces an index.html (not shown) that contains a
> table of warnings whose columns can be sorted with a mouse click.
> That table has a less polished look than the one in the wiki. If
> you are interested in getting the static analysis results on Adium
> where you can sort the results, you can easily just rerun the tool.
> If anyone is interested in making the tool's output more polished,
> patches are certainly welcome. I don't pretend to be an HTML guru.
> On Jul 7, 2008, at 8:25 AM, Ted Kremenek wrote:
>> Hi Todd,
>> The table of results should already be sortable by column. Is this
>> not working for you? We use the sorttable.js script found at:
>> This only works if the sorttable.js is in the same directory as the
>> index.html that lists the set of warnings (scan-build copies this
>> over by default).
>> On Jul 7, 2008, at 7:02 AM, Todd Ransom wrote:
>>> I would like to see the output sorted by source file. For instance,
>>> if MyClass.m has 5 memory leaks reported then these leaks should all
>>> be next to one another so I don't have to hunt back and forth
>>> between files. And/or you could make the table of results sortable
>>> by column.
>>> Todd Ransom
>>> StoryMill & Montage Development
>>> Mariner Software
>>> On Jul 6, 2008, at 8:28 PM, Ted Kremenek wrote:
>>>> On Jul 4, 2008, at 12:17 AM, Holger Schurig wrote:
>>>>>> dereferences. Beyond improving the precision of the analyzer,
>>>>>> improving its output is also high on the todo list. (so any
>>>>>> suggestions are welcome!)
>>>>> Add links to descriptions. E.g., when who first visits this page
>>>>> sees "Dead store on ...". I can imagine that only a few people
>>>>> know what a dead store actually is.
>>>> Agreed. That's an excellent suggestion.
>>>> cfe-dev mailing list
>>>> cfe-dev at cs.uiuc.edu
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev