Wireshark-bugs: [Wireshark-bugs] [Bug 10907] New: Buildbot crash output: fuzz-2015-01-30-18636.p
Date: Sat, 31 Jan 2015 10:50:03 +0000
Bug ID 10907
Summary Buildbot crash output: fuzz-2015-01-30-18636.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2015-01-30-18636.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter buildbot-do-not-reply@wireshark.org

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2015-01-30-18636.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/8035-hartip_2_03072012.pcap

Build host information:
Linux wsbb04 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=3126
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=6940a9717cf7a6a88945dc684e4cb2428d280b85

Return value:  0

Dissector bug:  0

Valgrind error count:  3



Git commit
commit 6940a9717cf7a6a88945dc684e4cb2428d280b85
Author: Guy Harris <guy@alum.mit.edu>
Date:   Wed Jan 28 11:39:04 2015 -0800

    Go back to installing 5.2.3 for now.

    Change-Id: I1c798cd1a74aee559225fea1e4bc3694466de861
    Reviewed-on: https://code.wireshark.org/review/6836
    Reviewed-by: Guy Harris <guy@alum.mit.edu>


Command and args: ./tools/valgrind-wireshark.sh 

==21413== Memcheck, a memory error detector
==21413== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==21413== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==21413== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2015-01-30-18636.pcap
==21413== 
==21413== Invalid read of size 4
==21413==    at 0x72381E1: jsmn_parse (jsmn.c:266)
==21413==    by 0x6B07BE9: dissect_json_heur (packet-json.c:585)
==21413==    by 0x66F9269: dissector_try_heuristic (packet.c:2059)
==21413==    by 0x68BA141: dissect_db_lsp_disc (packet-db-lsp.c:182)
==21413==    by 0x66F7223: call_dissector_through_handle (packet.c:630)
==21413==    by 0x66F7CB4: call_dissector_work (packet.c:717)
==21413==    by 0x66F83FB: dissector_try_uint_new (packet.c:1149)
==21413==    by 0x66F8446: dissector_try_uint (packet.c:1175)
==21413==    by 0x6E419B9: decode_udp_ports (packet-udp.c:532)
==21413==    by 0x6E42202: dissect (packet-udp.c:878)
==21413==    by 0x66F7223: call_dissector_through_handle (packet.c:630)
==21413==    by 0x66F7CB4: call_dissector_work (packet.c:717)
==21413==  Address 0x1295ee30 is 16 bytes before a block of size 16,384 alloc'd
==21413==    at 0x4C2AB80: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==21413==    by 0x9BD4610: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0)
==21413==    by 0x723D38B: wmem_simple_alloc (wmem_allocator_simple.c:55)
==21413==    by 0x6B07BC3: dissect_json_heur (packet-json.c:582)
==21413==    by 0x66F9269: dissector_try_heuristic (packet.c:2059)
==21413==    by 0x68BA141: dissect_db_lsp_disc (packet-db-lsp.c:182)
==21413==    by 0x66F7223: call_dissector_through_handle (packet.c:630)
==21413==    by 0x66F7CB4: call_dissector_work (packet.c:717)
==21413==    by 0x66F83FB: dissector_try_uint_new (packet.c:1149)
==21413==    by 0x66F8446: dissector_try_uint (packet.c:1175)
==21413==    by 0x6E419B9: decode_udp_ports (packet-udp.c:532)
==21413==    by 0x6E42202: dissect (packet-udp.c:878)
==21413== 
==21413== 
==21413== HEAP SUMMARY:
==21413==     in use at exit: 1,237,109 bytes in 29,964 blocks
==21413==   total heap usage: 622,113 allocs, 592,149 frees, 51,518,781 bytes
allocated
==21413== 
==21413== LEAK SUMMARY:
==21413==    definitely lost: 5,040 bytes in 247 blocks
==21413==    indirectly lost: 37,880 bytes in 108 blocks
==21413==      possibly lost: 0 bytes in 0 blocks
==21413==    still reachable: 1,194,189 bytes in 29,609 blocks
==21413==         suppressed: 0 bytes in 0 blocks
==21413== Rerun with --leak-check=full to see details of leaked memory
==21413== 
==21413== For counts of detected and suppressed errors, rerun with: -v
==21413== ERROR SUMMARY: 3 errors from 1 contexts (suppressed: 0 from 0)

[ no debug trace ]


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