Joerg Sonnenberger wrote in
:
|Am Fri, Jan 21, 2022 at 12:45:56AM +0100 schrieb Steffen Nurpmeso:
|> Fwiw, i have been astonished by this thread. I found scan-build
|> to generate a lot of false warnings, so much indeed that i stopped
|> using it .. in summer 2017.
|
|I've spend time on
Am Fri, Jan 21, 2022 at 12:45:56AM +0100 schrieb Steffen Nurpmeso:
> Fwiw, i have been astonished by this thread. I found scan-build
> to generate a lot of false warnings, so much indeed that i stopped
> using it .. in summer 2017.
I've spend time on the static analyzer output in NetBSD and I
Hello.
Steffen Nurpmeso wrote in
<20220121154612.frou2%stef...@sdaoden.eu>:
|Andre Smagin wrote in
| <20220120231806.0463e0c792db3e3e5fc07...@smagin.com>:
||On Fri, 21 Jan 2022 00:45:56 +0100
||Steffen Nurpmeso wrote:
||> I found scan-build to generate a lot of false warnings, so much
Andre Smagin wrote in
<20220120231806.0463e0c792db3e3e5fc07...@smagin.com>:
|On Fri, 21 Jan 2022 00:45:56 +0100
|Steffen Nurpmeso wrote:
|
|> I found scan-build to generate a lot of false warnings, so much indeed
|> that i stopped using it .. in summer 2017.
|
|You, and most others, (no
On Fri, 21 Jan 2022 00:45:56 +0100
Steffen Nurpmeso wrote:
> I found scan-build to generate a lot of false warnings, so much indeed
> that i stopped using it .. in summer 2017.
You, and most others, (no sarcasm at all here) are much better
at C than I will ever be. I am not even at "amateur"
Alexander Bluhm wrote in
:
|On Fri, Jan 14, 2022 at 05:59:24PM +0100, Claudio Jeker wrote:
|> On Fri, Jan 14, 2022 at 04:44:49PM +, Stuart Henderson wrote:
|>> On 2022/01/14 16:52, Rafael Sadowski wrote:
|>>> On Fri Jan 14, 2022 at 03:17:21PM +0100, Tobias Heider wrote:
| clang ships
On Fri, Jan 14, 2022 at 05:59:24PM +0100, Claudio Jeker wrote:
> On Fri, Jan 14, 2022 at 04:44:49PM +, Stuart Henderson wrote:
> > On 2022/01/14 16:52, Rafael Sadowski wrote:
> > > On Fri Jan 14, 2022 at 03:17:21PM +0100, Tobias Heider wrote:
> > > > Hi,
> > > >
> > > > clang ships with a
On Fri, Jan 14, 2022 at 04:44:49PM +, Stuart Henderson wrote:
> On 2022/01/14 16:52, Rafael Sadowski wrote:
> > On Fri Jan 14, 2022 at 03:17:21PM +0100, Tobias Heider wrote:
> > > Hi,
> > >
> > > clang ships with a pretty useful static analyzer to find all kinds of bugs
> > > in C and C++
On 2022/01/14 16:52, Rafael Sadowski wrote:
> On Fri Jan 14, 2022 at 03:17:21PM +0100, Tobias Heider wrote:
> > Hi,
> >
> > clang ships with a pretty useful static analyzer to find all kinds of bugs
> > in C and C++ code:
> >
> > https://clang-analyzer.llvm.org/
> >
> > I use it regularly to
On Fri Jan 14, 2022 at 03:17:21PM +0100, Tobias Heider wrote:
> Hi,
>
> clang ships with a pretty useful static analyzer to find all kinds of bugs
> in C and C++ code:
>
> https://clang-analyzer.llvm.org/
>
> I use it regularly to check my own diffs and found plenty of bugs I could
> have
On Fri, Jan 14, 2022 at 03:17:21PM +0100, Tobias Heider wrote:
> Hi,
>
> clang ships with a pretty useful static analyzer to find all kinds of bugs
> in C and C++ code:
>
> https://clang-analyzer.llvm.org/
>
> I use it regularly to check my own diffs and found plenty of bugs I could
> have
On Fri, 14 Jan 2022 14:53:21 +, Visa Hankala wrote:
> I think the tool is useful. However, installing it from ports is good
> enough for me.
Same here.
- todd
On Fri, Jan 14, 2022 at 03:17:21PM +0100, Tobias Heider wrote:
> Hi,
>
> clang ships with a pretty useful static analyzer to find all kinds of bugs
> in C and C++ code:
>
> https://clang-analyzer.llvm.org/
>
> I use it regularly to check my own diffs and found plenty of bugs I could
> have
Hi,
clang ships with a pretty useful static analyzer to find all kinds of bugs
in C and C++ code:
https://clang-analyzer.llvm.org/
I use it regularly to check my own diffs and found plenty of bugs I could
have missed otherwise. While we have the code in base we don't actually
build it into our
14 matches
Mail list logo
