The record changes tripped a new Coverity issue. Please fix it.
--joel
-- Forwarded message -
From:
Date: Wed, Nov 13, 2024, 1:31 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with
Any suggestions on how to address these?
-- Forwarded message -
From:
Date: Sun, Dec 24, 2023, 1:18 PM
Subject: New Defects reported by Coverity Scan for RTEMS-Tools
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS-Tools
found with Coverity Scan.
39
Done.
On Mon, Aug 21, 2023 at 8:57 PM Chris Johns wrote:
> On 22/8/2023 10:02 am, Gedare Bloom wrote:
> > flag it as a false positive.
>
> I agree.
>
> > g7 is a global register that is reserved for system / compiler use in
> > the sparc ABI
>
> The reigster is set up by the operating system out
On 22/8/2023 10:02 am, Gedare Bloom wrote:
> flag it as a false positive.
I agree.
> g7 is a global register that is reserved for system / compiler use in
> the sparc ABI
The reigster is set up by the operating system out of the view of Coverity. I
took the code from:
https://git.rtems.org/rtem
flag it as a false positive.
g7 is a global register that is reserved for system / compiler use in
the sparc ABI
On Mon, Aug 21, 2023 at 2:17 PM Joel Sherrill wrote:
>
> Moving it back to devel@.
>
> It appears to be from this bit of magic in the same file which implements it
> using a direct r
Moving it back to devel@.
It appears to be from this bit of magic in the same file which implements
it using a direct reference to register g7.
#elif defined(__sparc__)
#include
# define __get_tls() ({ void** __val; register uintptr_t g7 __asm__( "g7"
); __val = (void**) g7; __val; })
I honestl
New Coverity issue
-- Forwarded message -
From:
Date: Wed, Aug 2, 2023, 12:22 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Coverity Scan.
1 new defect(s) introduced to RTEMS f
On Mon, Jul 17, 2023 at 1:15 PM Gedare Bloom wrote:
> Sebastian fixed it now. The local variable was shadowed. Another good
> reason to keep local variables at the start of a function ;)
>
+1
The first time I saw GCC spit this warning out was for some particularly
horrible code. It had shadowed
Sebastian fixed it now. The local variable was shadowed. Another good
reason to keep local variables at the start of a function ;)
On Sat, Jul 15, 2023 at 9:38 AM Joel Sherrill wrote:
>
>
> The recent grlib changes introduced a Coverity issues.
>
> -- Forwarded message -
> From:
The recent grlib changes introduced a Coverity issues.
-- Forwarded message -
From:
Date: Sat, Jul 15, 2023 at 12:22 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Coverity Scan.
At least one of them is clear how to fix.
-- Forwarded message -
From:
Date: Tue, May 16, 2023, 12:57 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Coverity Scan.
2 new defect(
Hello Joel,
On 10.05.23 15:33, Joel Sherrill wrote:
Sebastian I know this is third party code that you just imported but
this looks like a potentially serious issue.
Does anyone see how this could occur? Have a suggestion?
Minimum is to report it upstream. I did that years ago with another
Hi
Sebastian I know this is third party code that you just imported but this
looks like a potentially serious issue.
Does anyone see how this could occur? Have a suggestion?
Minimum is to report it upstream. I did that years ago with another issue
in zlib.
--joel
-- Forwarded message -
New issue from Coveriry.
I vaguely recall that JFFS2 uses dynamic checks for things that static
would work and Coveriry spots the dead code
-- Forwarded message -
From:
Date: Sun, Mar 19, 2023, 10:59 PM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please f
Chris,
I don't think Coverity was pleased with your recent changes to edit.c :)
--joel
-- Forwarded message -
From:
Date: Wed, Nov 23, 2022 at 1:15 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced t
Hi,
Thanks Coverity for picking up I forgot to add the new error string. :)
I will push the 1 line change.
Chris
On 10/10/2022 10:46 pm, Joel Sherrill wrote:
>
> -- Forwarded message -
> From: mailto:scan-ad...@coverity.com>>
> Date: Mon, Oct 10, 2022, 12:22 AM
> Subject: New D
-- Forwarded message -
From:
Date: Mon, Oct 10, 2022, 12:22 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Coverity Scan.
1 new defect(s) introduced to RTEMS found with Coverity
Again.. issue lurking spotted by new version of Coverity Scan.
Please look at it and fix.
-- Forwarded message -
From:
Date: Mon, Aug 29, 2022 at 5:55 PM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduce
I don't think this is due to a recent addition. I just upgraded to a new
version of the Coverity analysis tool.
Does anyone see a fix for this?
--joel
-- Forwarded message -
From:
Date: Mon, Aug 29, 2022 at 5:14 PM
Subject: New Defects reported by Coverity Scan for RTEMS-Tools
To
-- Forwarded message -
From:
Date: Wed, Jun 22, 2022, 1:54 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Coverity Scan.
2 new defect(s) introduced to RTEMS found with Coverity S
I am not sure why these popped up now but some indicate logic errors
in the code cited.
--joel
-- Forwarded message -
From:
Date: Thu, Jul 15, 2021 at 12:26 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) intr
-- Forwarded message -
From:
Date: Tue, Mar 23, 2021 at 12:22 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Coverity Scan.
3 new defect(s) introduced to RTEMS found with Coverit
Luckily I think it is an easy one. Checking if an unsigned value is less
than 0.
Look back in the history. Ryan may have fixed it once and you just
accidentally
reverted it. He fixed a handful like this.
I'm sorry you were the first to be caught by it but I am thrilled to have
Coverity
run automa
yes, it must have, so I will look into that.
/Daniel
On 2021-03-12 14:07, Joel Sherrill wrote:
Without looking, I would assume this was introduced by Daniel's recent
patches.
-- Forwarded message -
From: mailto:scan-ad...@coverity.com>>
Date: Fri, Mar 12, 2021, 12:55
Without looking, I would assume this was introduced by Daniel's recent
patches.
-- Forwarded message -
From:
Date: Fri, Mar 12, 2021, 12:55 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS fo
fyi; I should see if I can get this put to the list directly...
-- Forwarded message -
From:
Date: Thu, Jan 28, 2021 at 11:59 AM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Cover
FYI
-- Forwarded message -
From:
Date: Wed, Jan 27, 2021, 9:21 PM
Subject: New Defects reported by Coverity Scan for RTEMS
To:
Hi,
Please find the latest report on new defect(s) introduced to RTEMS found
with Coverity Scan.
11 new defect(s) introduced to RTEMS found with Cove
On 09/12/2020 10:11, Sebastian Huber wrote:
On 08/12/2020 19:10, Gedare Bloom wrote:
Hi all,
I get a text report on new defects from Coverity. I don't know how I
managed to sign up for it, and I'm not sure I can get it sent to any
list automatically, but here is the current updated new def
On 08/12/2020 19:10, Gedare Bloom wrote:
Hi all,
I get a text report on new defects from Coverity. I don't know how I
managed to sign up for it, and I'm not sure I can get it sent to any
list automatically, but here is the current updated new defects. Just
looks like two new ones related to
Hi all,
I get a text report on new defects from Coverity. I don't know how I
managed to sign up for it, and I'm not sure I can get it sent to any list
automatically, but here is the current updated new defects. Just looks like
two new ones related to static assertions.
-- Forwarded messag
30 matches
Mail list logo
