Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

decode_ssl_received_bytes: Conditional jump or move depends on uninitialised value #216

Open
alepez opened this issue Feb 21, 2018 · 1 comment

Comments

@alepez
Copy link

alepez commented Feb 21, 2018

Hi,
I've just hit this error. I'm using valgrind to debug memory access. I'm using https://github.com/Azure/azure-event-hubs-c that depends on this project (https://github.com/Azure/azure-uamqp-).

Valgrind finds an error: "Conditional jump or move depends on uninitialised value(s) ". This is the backtrace:

==29644== Conditional jump or move depends on uninitialised value(s)
==29644==    at 0x4C2AB2D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==29644==    by 0x49A07D: frame_codec_receive_bytes (in _omitted_binary_name_)
==29644==    by 0x496BF1: connection_byte_received (in _omitted_binary_name_)
==29644==    by 0x496CA3: connection_on_bytes_received (in _omitted_binary_name_)
==29644==    by 0x4A3512: on_underlying_io_bytes_received (in _omitted_binary_name_)
==29644==    by 0x4BB1CD: decode_ssl_received_bytes (in _omitted_binary_name_)
==29644==    by 0x4BB28A: on_underlying_io_bytes_received (in _omitted_binary_name_)
==29644==    by 0x4C0957: socketio_dowork (in _omitted_binary_name_)
==29644==    by 0x4B2689: xio_dowork (in _omitted_binary_name_)
==29644==    by 0x4BC521: tlsio_openssl_dowork (in _omitted_binary_name_)
==29644==    by 0x4B2689: xio_dowork (in _omitted_binary_name_)
==29644==    by 0x4A4F42: saslclientio_dowork (in _omitted_binary_name_)
==29644==    by 0x4B2689: xio_dowork (in _omitted_binary_name_)
==29644==    by 0x4990B0: connection_dowork (in _omitted_binary_name_)
==29644==    by 0x470B01: EventHubClient_LL_DoWork (in _omitted_binary_name_)
==29644==    by 0x46B9FC: EventhubClientThread (in _omitted_binary_name_)
==29644==    by 0x4B9134: ThreadWrapper (in _omitted_binary_name_)
==29644==    by 0x567F183: start_thread (pthread_create.c:312)
==29644==    by 0x6630FFC: clone (clone.S:111)
==29644==  Uninitialised value was created by a stack allocation
==29644==    at 0x531EF77: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)

At this point I don't know if this is actually an issue. But it may be.

@dcristoloveanu
Copy link
Member

Hi @alepez

Thanks for reporting this and sorry for the delay, I was out of office for the past days.
Which sample from the event hubs C SDK have you run, so that I make sure I repro the same?

At the moment I will assume it is the send sample and will try to repro with that.

Thanks,
/Dan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants