You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/bits/string_fortified.h:29:10: warning: '__builtin___memcpy_chk' offset [64, 128] is out of the bounds [0, 13] [-Warray-bounds]
* Please do not file a Gentoo bug and instead report the above QA
* issues directly to the upstream developers of this software.
* Homepage: https://github.com/nabla-c0d3/nassl
I received that warning message during compilation, something need to be investigated
/usr/include/bits/string_fortified.h is installed by sys-libs/glibc-2.34-r13, FYI
The text was updated successfully, but these errors were encountered:
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* /usr/include/bits/string_fortified.h:29:10: warning: '__builtin___memcpy_chk' forming offset 128 is out of the bounds [0, 128] of object 'hmac_pad' with type 'unsigned char[128]' [-Warray-bounds]
* /usr/include/bits/string_fortified.h:29:10: warning: '__builtin___memcpy_chk' offset [64, 128] is out of the bounds [0, 13] [-Warray-bounds]
* QA Notice: Package triggers severe warnings which indicate that it
* may exhibit random runtime failures.
* s3_srvr.c:1931:13: warning: '__builtin_strncpy' specified bound depends on the length of the source argument [-Wstringop-truncation]
* passwd.c:309:5: warning: '__builtin___strncat_chk' output may be truncated copying 4 bytes from a string of length 4 [-Wstringop-truncation]
* nassl/_nassl/nassl_SSL_CTX.c:251:5: warning: ‘__builtin_strncpy’ specified bound depends on the length of the source argument [-Wstringop-truncation]
I received that warning message during compilation, something need to be investigated
/usr/include/bits/string_fortified.h is installed by sys-libs/glibc-2.34-r13, FYI
The text was updated successfully, but these errors were encountered: