This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Clang static analyzer results
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Tue, 3 Jul 2012 18:12:35 -0400
- Subject: Re: Clang static analyzer results
- References: <1327661801.6868.46.camel@YAAKOV04> <20120702200433.GA9487@ednor.casa.cgf.cx> <1341352075.5384.8.camel@YAAKOV04>
- Reply-to: cygwin-developers at cygwin dot com
On Tue, Jul 03, 2012 at 04:47:55PM -0500, Yaakov (Cygwin/X) wrote:
>On Mon, 2012-07-02 at 16:04 -0400, Christopher Faylor wrote:
>> On Fri, Jan 27, 2012 at 04:56:41AM -0600, Yaakov (Cygwin/X) wrote:
>> >I just added the clang-analyzer to the pending LLVM/Clang ITP, and what
>> >better way to test it than on the Cygwin codebase itself. Here are the
>> >results for CVS HEAD as of yesterday:
>> >
>> >http://cygwin-ports.sourceforge.net/scan-build/
>> >
>> Many months later, I thought maybe the above might have uncovered
>> something which would shed some light on the stack problems that I
>> noted. It didn't but I did take a swing through this report and
>> eliminated some of the more obvious issues.
>>
>> Any chance, you could rerun this Yaakov?
>
>Done and uploaded to the same location.
Did you update your tree before doing this? It seems like some of the
problems that I fixed yesterday are still there.
>> I promise to look at it within the next three months if so. That
>> will more than half the amount of time it took me to look at your
>> last report.
>
>:-)
>
>> Btw, Clang doesn't actually build a usable version of Cygwin does it?
>
>I haven't tried yet. Clang didn't handle PE C++ exceptions as of 3.0:
>
>http://cygwin.com/ml/cygwin/2012-02/msg00025.html
AFAIK, we don't use C++ exceptions in the DLL do we?
cgf