Some warnings at GCC-11.x linux compilation

[ROBERT-MCDOWELL]

src/objects.c: In function ‘use_client_socket’:
src/objects.c:1449:17: warning: ‘memcpy’ offset [0, 31] is out of the bounds [0, 0] [-Warray-bounds]
 1449 |                 memcpy(user->scram_ClientKey, scram_client_key, sizeof(user->scram_ClientKey));
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/objects.c:1450:17: warning: ‘memcpy’ offset [0, 31] is out of the bounds [0, 0] [-Warray-bounds]
 1450 |                 memcpy(user->scram_ServerKey, scram_server_key, sizeof(user->scram_ServerKey));
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

thanks

[petere]

I see it too, but I don't think this warning message makes sense. It's essentially claiming that user->scram_ClientKey and user->scram_ServerKey have size 0. It's even weirder when you set -Warray-bounds=0, then you get

src/objects.c:1449:17: warning: '__builtin_memcpy' writing 32 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
src/objects.c:1450:17: warning: '__builtin_memcpy' writing 32 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]

which appears to be the same compiler confusion in a different form.

[ROBERT-MCDOWELL]

I recalll that many apps had to update memcpy since gcc11 is more strict