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
[185/190] Linking target codec/console/dec/h264dec
In file included from ../subprojects/googletest-release-1.8.0/googletest/include/gtest/internal/gtest-port.h:263,
from ../subprojects/googletest-release-1.8.0/googletest/include/gtest/internal/gtest-internal.h:40,
from ../subprojects/googletest-release-1.8.0/googletest/include/gtest/gtest.h:58,
from ../test/api/encode_decode_api_test.cpp:1:
In function 'void* memset(void*, int, size_t)',
inlined from 'int SimulateNALLoss(const unsigned char*, int&, std::vector<SLost_Sim>*, const char*, bool, int&, bool&)' at ../test/api/encode_decode_api_test.cpp:387:10:
/usr/include/fortify/string.h:75:32: warning: 'void* __builtin_memset(void*, int, long unsigned int)' specified size between 18446744071562067968 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
75 | return __builtin_memset(__d, __c, __n);
| ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
[186/190] Linking target test/encoder/test_encoder
This is some buffer overflow error?
The error is present in the current "head/master" of the git repo and the last release tarball and can be reproduced with an alpine linux docker container.
This is the Dockerfile I am using for the container that gets this error:
Using the git repositorys head, the ninja build fails because the warning is treated as error.
Using the last source tarball I get a warning with the same content but the build continues.
The text was updated successfully, but these errors were encountered:
This is the error:
This is some buffer overflow error?
The error is present in the current "head/master" of the git repo and the last release tarball and can be reproduced with an alpine linux docker container.
This is the Dockerfile I am using for the container that gets this error:
To compile I run:
Using the git repositorys head, the ninja build fails because the warning is treated as error.
Using the last source tarball I get a warning with the same content but the build continues.
The text was updated successfully, but these errors were encountered: