Wireshark-bugs: [Wireshark-bugs] [Bug 10261] Buildbot crash output: fuzz-2014-07-05-22241.pcap

Date: Sun, 06 Jul 2014 13:02:14 +0000

changed bug 10261

What Removed Added
CC   [email protected]

Comment # 1 on bug 10261 from
==2243== 4,224 bytes in 352 blocks are definitely lost in loss record 3,238 of
3,258
==2243==    at 0x4C2AB80: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2243==    by 0xA09B610: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
==2243==    by 0x691AA6D: rpc_init_proc_table (packet-rpc.c:360)
==2243==    by 0x6850B9E: reg_callback (packet-nfs.c:10373)
==2243==    by 0x685C667: dissect_nfs4_compound_call (packet-nfs.c:7562)
==2243==    by 0x691A2E1: call_dissect_function (packet-rpc.c:1443)
==2243==    by 0x691BD46: dissect_rpc_message (packet-rpc.c:2790)
==2243==    by 0x691DAD8: call_message_dissector.constprop.11
(packet-rpc.c:3054)
==2243==    by 0x691DDE0: dissect_rpc_fragment.part.3.constprop.10
(packet-rpc.c:3440)
==2243==    by 0x691E12C: dissect_rpc_tcp_common (packet-rpc.c:3683)
==2243==    by 0x691E286: dissect_rpc_tcp (packet-rpc.c:3751)
==2243==    by 0x6322B5E: call_dissector_through_handle (packet.c:622)
==2243== 
==2243== 4,224 bytes in 352 blocks are definitely lost in loss record 3,239 of
3,258
==2243==    at 0x4C2AB80: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2243==    by 0xA09B610: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
==2243==    by 0x691AA6D: rpc_init_proc_table (packet-rpc.c:360)
==2243==    by 0x685C667: dissect_nfs4_compound_call (packet-nfs.c:7562)
==2243==    by 0x691A2E1: call_dissect_function (packet-rpc.c:1443)
==2243==    by 0x691BD46: dissect_rpc_message (packet-rpc.c:2790)
==2243==    by 0x691DAD8: call_message_dissector.constprop.11
(packet-rpc.c:3054)
==2243==    by 0x691DDE0: dissect_rpc_fragment.part.3.constprop.10
(packet-rpc.c:3440)
==2243==    by 0x691E12C: dissect_rpc_tcp_common (packet-rpc.c:3683)
==2243==    by 0x691E286: dissect_rpc_tcp (packet-rpc.c:3751)
==2243==    by 0x6322B5E: call_dissector_through_handle (packet.c:622)
==2243==    by 0x6323444: call_dissector_work (packet.c:713)
==2243== 
==2243== 5,928 (1,824 direct, 4,104 indirect) bytes in 57 blocks are definitely
lost in loss record 3,244 of 3,258
==2243==    at 0x4C2AB80: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2243==    by 0xA09B610: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
==2243==    by 0x691AB79: rpc_init_prog (packet-rpc.c:437)
==2243==    by 0x6850B85: reg_callback (packet-nfs.c:10366)
==2243==    by 0x685C667: dissect_nfs4_compound_call (packet-nfs.c:7562)
==2243==    by 0x691A2E1: call_dissect_function (packet-rpc.c:1443)
==2243==    by 0x691BD46: dissect_rpc_message (packet-rpc.c:2790)
==2243==    by 0x691DAD8: call_message_dissector.constprop.11
(packet-rpc.c:3054)
==2243==    by 0x691DDE0: dissect_rpc_fragment.part.3.constprop.10
(packet-rpc.c:3440)
==2243==    by 0x691E12C: dissect_rpc_tcp_common (packet-rpc.c:3683)
==2243==    by 0x691E2D0: dissect_rpc_tcp_heur (packet-rpc.c:3731)
==2243==    by 0x6324979: dissector_try_heuristic (packet.c:2028)
==2243== 
==2243== 8,448 bytes in 352 blocks are definitely lost in loss record 3,248 of
3,258
==2243==    at 0x4C2AB80: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2243==    by 0xA09B610: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
==2243==    by 0x691AA87: rpc_init_proc_table (packet-rpc.c:365)
==2243==    by 0x6850B9E: reg_callback (packet-nfs.c:10373)
==2243==    by 0x685C667: dissect_nfs4_compound_call (packet-nfs.c:7562)
==2243==    by 0x691A2E1: call_dissect_function (packet-rpc.c:1443)
==2243==    by 0x691BD46: dissect_rpc_message (packet-rpc.c:2790)
==2243==    by 0x691DAD8: call_message_dissector.constprop.11
(packet-rpc.c:3054)
==2243==    by 0x691DDE0: dissect_rpc_fragment.part.3.constprop.10
(packet-rpc.c:3440)
==2243==    by 0x691E12C: dissect_rpc_tcp_common (packet-rpc.c:3683)
==2243==    by 0x691E286: dissect_rpc_tcp (packet-rpc.c:3751)
==2243==    by 0x6322B5E: call_dissector_through_handle (packet.c:622)
==2243== 
==2243== 8,448 bytes in 352 blocks are definitely lost in loss record 3,249 of
3,258
==2243==    at 0x4C2AB80: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2243==    by 0xA09B610: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
==2243==    by 0x691AA87: rpc_init_proc_table (packet-rpc.c:365)
==2243==    by 0x685C667: dissect_nfs4_compound_call (packet-nfs.c:7562)
==2243==    by 0x691A2E1: call_dissect_function (packet-rpc.c:1443)
==2243==    by 0x691BD46: dissect_rpc_message (packet-rpc.c:2790)
==2243==    by 0x691DAD8: call_message_dissector.constprop.11
(packet-rpc.c:3054)
==2243==    by 0x691DDE0: dissect_rpc_fragment.part.3.constprop.10
(packet-rpc.c:3440)
==2243==    by 0x691E12C: dissect_rpc_tcp_common (packet-rpc.c:3683)
==2243==    by 0x691E286: dissect_rpc_tcp (packet-rpc.c:3751)
==2243==    by 0x6322B5E: call_dissector_through_handle (packet.c:622)
==2243==    by 0x6323444: call_dissector_work (packet.c:713)
==2243== 
==2243== 18,304 (5,632 direct, 12,672 indirect) bytes in 176 blocks are
definitely lost in loss record 3,256 of 3,258
==2243==    at 0x4C2AB80: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2243==    by 0xA09B610: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
==2243==    by 0x691AB79: rpc_init_prog (packet-rpc.c:437)
==2243==    by 0x6850B85: reg_callback (packet-nfs.c:10366)
==2243==    by 0x685C667: dissect_nfs4_compound_call (packet-nfs.c:7562)
==2243==    by 0x691A2E1: call_dissect_function (packet-rpc.c:1443)
==2243==    by 0x691BD46: dissect_rpc_message (packet-rpc.c:2790)
==2243==    by 0x691DAD8: call_message_dissector.constprop.11
(packet-rpc.c:3054)
==2243==    by 0x691DDE0: dissect_rpc_fragment.part.3.constprop.10
(packet-rpc.c:3440)
==2243==    by 0x691E12C: dissect_rpc_tcp_common (packet-rpc.c:3683)
==2243==    by 0x691E286: dissect_rpc_tcp (packet-rpc.c:3751)
==2243==    by 0x6322B5E: call_dissector_through_handle (packet.c:622)


You are receiving this mail because:
  • You are watching all bug changes.