Comment # 2
on bug 9120
from Evan Huus
Uninitialized access fixed in r51865. There are still the failing dissector
assertions which I haven't looked at yet, as well as some substantial memory
leaks:
==4774== 81,144 (38,808 direct, 42,336 indirect) bytes in 441 blocks are
definitely lost in loss record 23,877 of 23,886
==4774== at 0x4C2A2DB: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4774== by 0x9444D40: g_malloc (gmem.c:104)
==4774== by 0x945A91D: g_slice_alloc (gslice.c:1016)
==4774== by 0x942EB8D: g_hash_table_new_full (ghash.c:653)
==4774== by 0x6A5CE7E: dissect_smb2 (packet-smb2.c:6809)
==4774== by 0x6A5D186: dissect_smb2_heur (packet-smb2.c:7082)
==4774== by 0x6457BF7: dissector_try_heuristic (packet.c:1846)
==4774== by 0x68D4C14: dissect_netbios_payload (packet-netbios.c:1055)
==4774== by 0x689FF9B: dissect_nbss_packet (packet-nbns.c:1612)
==4774== by 0x68A017A: dissect_nbss (packet-nbns.c:1816)
==4774== by 0x6455FD3: call_dissector_through_handle (packet.c:492)
==4774== by 0x645668F: call_dissector_work (packet.c:586)
==4774==
==4774== 82,296 (38,808 direct, 43,488 indirect) bytes in 441 blocks are
definitely lost in loss record 23,878 of 23,886
==4774== at 0x4C2A2DB: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4774== by 0x9444D40: g_malloc (gmem.c:104)
==4774== by 0x945A91D: g_slice_alloc (gslice.c:1016)
==4774== by 0x942EB8D: g_hash_table_new_full (ghash.c:653)
==4774== by 0x6A5CE35: dissect_smb2 (packet-smb2.c:6805)
==4774== by 0x6A5D186: dissect_smb2_heur (packet-smb2.c:7082)
==4774== by 0x6457BF7: dissector_try_heuristic (packet.c:1846)
==4774== by 0x68D4C14: dissect_netbios_payload (packet-netbios.c:1055)
==4774== by 0x689FF9B: dissect_nbss_packet (packet-nbns.c:1612)
==4774== by 0x68A017A: dissect_nbss (packet-nbns.c:1816)
==4774== by 0x6455FD3: call_dissector_through_handle (packet.c:492)
==4774== by 0x645668F: call_dissector_work (packet.c:586)
==4774==
==4774== 88,248 (38,808 direct, 49,440 indirect) bytes in 441 blocks are
definitely lost in loss record 23,879 of 23,886
==4774== at 0x4C2A2DB: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4774== by 0x9444D40: g_malloc (gmem.c:104)
==4774== by 0x945A91D: g_slice_alloc (gslice.c:1016)
==4774== by 0x942EB8D: g_hash_table_new_full (ghash.c:653)
==4774== by 0x6A5CE5A: dissect_smb2 (packet-smb2.c:6807)
==4774== by 0x6A5D186: dissect_smb2_heur (packet-smb2.c:7082)
==4774== by 0x6457BF7: dissector_try_heuristic (packet.c:1846)
==4774== by 0x68D4C14: dissect_netbios_payload (packet-netbios.c:1055)
==4774== by 0x689FF9B: dissect_nbss_packet (packet-nbns.c:1612)
==4774== by 0x68A017A: dissect_nbss (packet-nbns.c:1816)
==4774== by 0x6455FD3: call_dissector_through_handle (packet.c:492)
==4774== by 0x645668F: call_dissector_work (packet.c:586)
==4774==
==4774== 100,728 (38,808 direct, 61,920 indirect) bytes in 441 blocks are
definitely lost in loss record 23,880 of 23,886
==4774== at 0x4C2A2DB: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4774== by 0x9444D40: g_malloc (gmem.c:104)
==4774== by 0x945A91D: g_slice_alloc (gslice.c:1016)
==4774== by 0x942EB8D: g_hash_table_new_full (ghash.c:653)
==4774== by 0x6A5CEA3: dissect_smb2 (packet-smb2.c:6811)
==4774== by 0x6A5D186: dissect_smb2_heur (packet-smb2.c:7082)
==4774== by 0x6457BF7: dissector_try_heuristic (packet.c:1846)
==4774== by 0x68D4C14: dissect_netbios_payload (packet-netbios.c:1055)
==4774== by 0x689FF9B: dissect_nbss_packet (packet-nbns.c:1612)
==4774== by 0x68A017A: dissect_nbss (packet-nbns.c:1816)
==4774== by 0x6455FD3: call_dissector_through_handle (packet.c:492)
==4774== by 0x645668F: call_dissector_work (packet.c:586)
You are receiving this mail because:
- You are watching all bug changes.
