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

valgrind reporting unitialized bytes sent #3

Closed
gladish opened this issue Feb 25, 2020 · 1 comment
Closed

valgrind reporting unitialized bytes sent #3

gladish opened this issue Feb 25, 2020 · 1 comment

Comments

@gladish
Copy link
Owner

gladish commented Feb 25, 2020

1582595558.856188 INFO -- Thread-9882: header:42 write_buffer:1076
==9882== Syscall param socketcall.sendto(msg) points to uninitialised byte(s)
==9882== at 0x5174DFA: sendto (sendto.c:27)
==9882== by 0x4E4D763: lifxSession_SendToInternal (lifx_session.c:456)
==9882== by 0x4E4E03C: lifxSession_BeginSendRequest (lifx_session.c:666)
==9882== by 0x108D26: main (async.c:67)
==9882== Address 0x586b386 is 38 bytes inside a block of size 1,076 alloc'd
==9882== at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==9882== by 0x4E423BD: lifxBuffer_Init (lifx_buffer.c:35)
==9882== by 0x4E4C962: lifxSession_Open (lifx_session.c:160)
==9882== by 0x108C87: main (async.c:50)
==9882==

@gladish
Copy link
Owner Author

gladish commented Feb 28, 2020

This was because the request being sent in from the test app wasn't initialized, and not a library issue

@gladish gladish closed this as completed Feb 28, 2020
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

1 participant