mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 10:05:29 +00:00
9b67d18f11
--read-var-info=yes is very memory and cpu intensive. This patch ensures that even witout --read-var-info=yes that the frame where the address point is reported in the address description. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13991
25 lines
916 B
Plaintext
25 lines
916 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
|
|
in frame #1, created by main (rfcomm.c:25)
|
|
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
|
|
in frame #1, created by main (rfcomm.c:25)
|
|
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
|
|
in frame #1, created by main (rfcomm.c:25)
|
|
Uninitialised value was created by a stack allocation
|
|
at 0x........: main (rfcomm.c:25)
|
|
|