Looks like edit.c may still have an issue since only one was eliminated.
Late here and I didn't check the Coverity report for sure.
-- Forwarded message -
From:
Date: Fri, Nov 25, 2022, 12:21 AM
Subject: Coverity Scan: Analysis completed for RTEMS
To:
Your request for anal
Another report from Coverity which shows more were introduced recently.
Unfortunately, their web UI doesn't help here. Per that, the most recently
"first detected" is from March and is in the jffs2 gc.c file:
135
const: At condition ({...; 0;}), the value of ({...; 0;}) must be equal to
0.
null
-- Forwarded message -
From:
Date: Mon, Mar 4, 2024 at 7:49 PM
Subject: Coverity Scan: Analysis completed for RTEMS
To:
Your request for analysis of RTEMS has been completed successfully.
The results are available at
https://u15810271.ct.sendgrid.net/ls/click?upn=u001.A
Another report from the new version. :(
-- Forwarded message -
From:
Date: Mon, Aug 29, 2022, 5:55 PM
Subject: Coverity Scan: Analysis completed for RTEMS
To:
Your request for analysis of RTEMS has been completed successfully.
The results are available at
https://u1581
Hi
After building new tools, I did a new Coverity Scan (
https://scan.coverity.com) run.
On a positive note, it looks like 7 were eliminated. There are now 143
outstanding.
I encourage everyone in the community to take a look and see if there are
any issues
flagged that they can analyse and elim
I don't think the build list has white listed the address these come from
so passing along there are new results.
-- Forwarded message -
From:
Date: Tue, Mar 12, 2019 at 12:23 PM
Subject: Coverity Scan: Analysis completed for RTEMS
To:
Your request for analysis of RTEMS ha
On 25/11/2022 5:40 pm, Joel Sherrill wrote:
> Looks like edit.c may still have an issue since only one was eliminated. Late
> here and I didn't check the Coverity report for sure.
With Coverity is there anyway to check changes or do we consider the issues
raised, attempt a solution then just keep
On Mon, Nov 28, 2022 at 3:33 PM Chris Johns wrote:
> On 25/11/2022 5:40 pm, Joel Sherrill wrote:
> > Looks like edit.c may still have an issue since only one was eliminated.
> Late
> > here and I didn't check the Coverity report for sure.
>
> With Coverity is there anyway to check changes or do w
-- Forwarded message -
From:
Date: Mon, Mar 4, 2024 at 5:56 PM
Subject: Coverity Scan: Analysis completed for RTEMS-Tools
To:
Your request for analysis of RTEMS-Tools has been completed
successfully.
The results are available at
https://u15810271.ct.sendgrid.net/ls/clic
-- Forwarded message -
From:
Date: Mon, Mar 4, 2024 at 7:51 PM
Subject: Coverity Scan: Analysis completed for RTEMS-Newlib
To:
Your request for analysis of RTEMS-Newlib has been completed
successfully.
The results are available at
https://u15810271.ct.sendgrid.net/ls/cl
On 13/3/19 7:18 am, Joel Sherrill wrote:
> I don't think the build list has white listed the address these come from so
> passing along there are new results.
Fixed, and sorry about forgetting to sort this out.
Chris
___
devel mailing list
devel@rtems.o
No problem. When I run it next time perhaps it will get through. :)
--joel
On Tue, Mar 12, 2019 at 4:42 PM Chris Johns wrote:
> On 13/3/19 7:18 am, Joel Sherrill wrote:
> > I don't think the build list has white listed the address these come
> from so
> > passing along there are new results.
>
12 matches
Mail list logo
