[cfe-users] cfe-users Digest, Vol 54, Issue 4

via cfe-users cfe-users at lists.llvm.org
Tue Aug 1 03:58:06 PDT 2017


Send cfe-users mailing list submissions to
cfe-users at lists.llvm.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users
or, via email, send a message with subject or body 'help' to
cfe-users-request at lists.llvm.org

You can reach the person managing the list at
cfe-users-owner at lists.llvm.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cfe-users digest..."


Today's Topics:

1. [analyzer] clang analyzer flag vs scan build
(Cyndy Ishida via cfe-users)
2. Re: [analyzer] clang analyzer flag vs scan build
(Anna Zaks via cfe-users)


----------------------------------------------------------------------

Message: 1
Date: Thu, 27 Jul 2017 19:33:09 +0000
From: Cyndy Ishida via cfe-users <cfe-users at lists.llvm.org>
To: "'cfe-users at lists.llvm.org'" <cfe-users at lists.llvm.org>
Cc: Nathan Wilson <nwilson at virtu.com>
Subject: [cfe-users] [analyzer] clang analyzer flag vs scan build
Message-ID: <7aa494e282cd400bb16420eb55b7a362 at CMKWSCTSMAIL01.kcg.com>
Content-Type: text/plain; charset="utf-8"

Hi,

I was trying to integrate the static analysis tools into a few of my
projects.
I started using scan-build, and couldn't  get it working on larger
projects,
even after exporting CXX & CC variables.
It just always reported 'no bugs found'.
Using clang++ --analyze, I was able to see warning messages.

On the smaller projects, I noticed that the errors were the same for both
the
compiler argument(--analyze) and the scan-build command.
Would anyone know if and how they would incur different warning reports?


Thanks!
-Cyndy Ishida
This message, including any attachments, is intended only for the personal
and
confidential use of the designated recipient(s) to which it is addressed.
This
communication may contain information that constitutes attorney work
product,
is privileged, confidential or otherwise protected from disclosure. If the
reader of this message is not the designated recipient, you are hereby
notified
that you have received this communication in error, and that any review,
dissemination, retention, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please
notify us by telephone at +1 212 418 0113 or by e-mail reply to the sender,
and
discard any paper copies and delete all electronic files of this
communication.
Virtu Financial LLC. <http://www.virtu.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/cfe-users/attachments/20170727/283903a0/attachm

ent-0001.html>

------------------------------

Message: 2
Date: Mon, 31 Jul 2017 09:50:20 -0700
From: Anna Zaks via cfe-users <cfe-users at lists.llvm.org>
To: Cyndy Ishida <cishida at virtu.com>
Cc: Nathan Wilson <nwilson at virtu.com>, "cfe-users at lists.llvm.org"
<cfe-users at lists.llvm.org>
Subject: Re: [cfe-users] [analyzer] clang analyzer flag vs scan build
Message-ID: <613D3739-7B43-4FAD-AB0C-1AA0996464F1 at apple.com>
Content-Type: text/plain; charset="utf-8"

I would recommend looking at the build script to see if there are any
errors
and if the source files where you expect errors to occur are being
analyzed.
(If it’s a makefile project, do not forget to run scan-build configure.)

Cheers,
Anna
> On Jul 27, 2017, at 12:33 PM, Cyndy Ishida via cfe-users
<cfe-users at lists.llvm.org> wrote:
>
> Hi,
>
> I was trying to integrate the static analysis tools into a few of my
projects.
> I started using scan-build, and couldn’t  get it working on larger
projects,
even after exporting CXX & CC variables.
> It just always reported ‘no bugs found’.
> Using clang++ --analyze, I was able to see warning messages.
>
> On the smaller projects, I noticed that the errors were the same for both
the
compiler argument(--analyze) and the scan-build command.
> Would anyone know if and how they would incur different warning reports?
>
>
> Thanks!
> -Cyndy Ishida
> This message, including any attachments, is intended only for the
personal
and confidential use of the designated recipient(s) to which it is
addressed.
This communication may contain information that constitutes attorney work
product, is privileged, confidential or otherwise protected from
disclosure. If
the reader of this message is not the designated recipient, you are hereby
notified that you have received this communication in error, and that any
review, dissemination, retention, distribution or copying of this
communication
is strictly prohibited. If you have received this communication in error,
please notify us by telephone at +1 212 418 0113 or by e-mail reply to the
sender, and discard any paper copies and delete all electronic files of
this
communication. Virtu Financial LLC.
<http://www.virtu.com/>_______________________________________________
> cfe-users mailing list
> cfe-users at lists.llvm.org <mailto:cfe-users at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users
<http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/cfe-users/attachments/20170731/c3bb8afe/attachm

ent-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
cfe-users mailing list
cfe-users at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users


------------------------------

End of cfe-users Digest, Vol 54, Issue 4
****************************************





More information about the cfe-users mailing list