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,
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
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
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
