Conditional jump or move depends on uninitialised value(s) in Socket_connect

[S-trace]

Hello.

Valgrind says:

==9657== Conditional jump or move depends on uninitialised value(s)
==9657==    at 0x12959D: Socket_connect (socket_linux.c:319)
==9657==    by 0x127F72: handleConnection (cs104_connection.c:733)
==9657==    by 0x488E181: start_thread (pthread_create.c:486)
==9657==    by 0x49C3B1E: clone (clone.S:95)
==9657==  Uninitialised value was created by a stack allocation
==9657==    at 0x12937F: Socket_connect (socket_linux.c:280)

Looks like it's happens after timed out connection attempt.

Thank you.

[mzillgith]

Hello, I cannot reproduce the problem. Can you provide more information how to reproduce? What version of Linux/libc are you using?

[S-trace]

I'm too could reproduce this problem only sometimes.

I'd used Kubuntu 19.04 AMD64 and libc was libc-bin:amd64 2.29-0ubuntu2 at the time I'd reported this issue.

This bug was detected in https://github.com/glial-iot/tarantool_iec_104_rock (in https://github.com/glial-iot/tarantool_iec_104_rock/commit/db7814a18aa1f7f131d1ab152ecb63a4c163cbfb commit, as i can remember) using standalone binary (libtest cmake target).