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
On 10/10/2022 9:22 pm, Frank Kühndel wrote:
> images/filesystem/tftpfs_usage.png:
> https://share.embedded-brains.de/index.php/s/fQ4WrLrqmBjcbwC
I have a greyed out image I cannot clearly see?
> images/filesystem/ftpfs_usage.svg:
> https://share.embedded-brains.de/index.php/s/xk7kArkm6mbjcn2
>
>
-- 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
Hello,
I am very sorry for having caused this trouble.
In my first email in June I wrote that there is an image which I did not
send as part of the patch (who is reviewing some 160KiB binary PNG data
and will the mailing list server accept that?). Yet, I forgot to mention
these files in my la
On 06/10/2022 10:23, Sebastian Huber wrote:
This patch set started with an 8 byte overwrite of the interrupt stack while
porting an application from RTEMS 5 to 6.
The overwrite was due to a mismatch of the size returned by
_TLS_Get_allocation_size() and the actual usage of the area. To fix this
