mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
Bug #320116. sockaddr_rc might contain some padding which might not be initialized. Explicitly check the sockaddr_rc fields are set. That also produces better diagnostics about which field is unitialized. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13404
22 lines
784 B
Plaintext
22 lines
784 B
Plaintext
Syscall param socketcall.bind(my_addr.sa_family) points to uninitialised byte(s)
|
|
...
|
|
by 0x........: main (rfcomm.c:40)
|
|
Address 0x........ is on thread 1's stack
|
|
Uninitialised value was created by a stack allocation
|
|
at 0x........: main (rfcomm.c:25)
|
|
|
|
Syscall param socketcall.bind(my_addr.rc_bdaddr) points to uninitialised byte(s)
|
|
...
|
|
by 0x........: main (rfcomm.c:44)
|
|
Address 0x........ is on thread 1's stack
|
|
Uninitialised value was created by a stack allocation
|
|
at 0x........: main (rfcomm.c:25)
|
|
|
|
Syscall param socketcall.bind(my_addr.rc_channel) points to uninitialised byte(s)
|
|
...
|
|
by 0x........: main (rfcomm.c:48)
|
|
Address 0x........ is on thread 1's stack
|
|
Uninitialised value was created by a stack allocation
|
|
at 0x........: main (rfcomm.c:25)
|
|
|