Wireshark-bugs: [Wireshark-bugs] [Bug 9027] Another fuzz failure in print_hex_data_buffer
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 11 Aug 2013 11:55:57 +0000

changed bug 9027

What Removed Added
CC   eapache@gmail.com
See Also   https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8825

Comment # 2 on bug 9027 from 
I this is basically the same type bug as 8825? Valgrind is giving me the same

==20618==  Address 0x131fa870 is 0 bytes inside a block of size * free'd
==20618==    at 0x4C2B60C: free (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20618==    by 0x640828D: fragment_add_work.isra.4 (reassemble.c:1176)
==20618==    by 0x640849B: fragment_add_common (reassemble.c:1360)
==20618==    by 0x6408AF7: fragment_add (reassemble.c:1380)
==20618==    by 0x6A30F19: dissect_tcp_payload (packet-tcp.c:1828)
==20618==    by 0x6A32AA9: dissect_tcp (packet-tcp.c:4889)
==20618==    by 0x63EA153: call_dissector_through_handle (packet.c:458)
==20618==    by 0x63EA80F: call_dissector_work (packet.c:552)
==20618==    by 0x63EB01B: dissector_try_uint_new (packet.c:969)
==20618==    by 0x63EB076: dissector_try_uint (packet.c:995)
==20618==    by 0x6768E35: dissect_ip (packet-ip.c:2413)
==20618==    by 0x63EA153: call_dissector_through_handle (packet.c:458)

However as with that one I can't make heads or tails of this. Something is
rotten in the state of the TCP reassembly code, but I can't seem to pin it
down.

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