Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12313] New: Buildbot crash output: fuzz-2016-03-30-14028.pcap

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	12313
Summary	Buildbot crash output: fuzz-2016-03-30-14028.pcap
Product	Wireshark
Version	unspecified
Hardware	x86-64
URL	https://www.wireshark.org/download/automated/captures/fuzz-2016-03-30-14028.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-2016-03-30-14028.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/8431-anyeth

Build host information:
Linux wsbb04 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_BUILDNUMBER=114
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.0/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=b25d52c888cdcb5aa64e6aff4fabf940fd935b5d

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit b25d52c888cdcb5aa64e6aff4fabf940fd935b5d
Author: Mike Frysinger <vapier@chromium.org>
Date:   Mon Mar 28 14:42:26 2016 -0400

    configure: fix non-POSIX test

    The == operator is not in POSIX -- it's an extension some shells support.

    Change-Id: Idb2be90307de783b4220cc7d91222b462c98dee4
    Reviewed-on: https://code.wireshark.org/review/14680
    Reviewed-by: Guy Harris <guy@alum.mit.edu>
    (cherry picked from commit c6fad4183c76259a20075c91599b02ce1a7b8e30)
    Reviewed-on: https://code.wireshark.org/review/14681


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

==32416== Memcheck, a memory error detector
==32416== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==32416== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==32416== Command:
/home/wireshark/builders/wireshark-2.0-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.0/fuzz-2016-03-30-14028.pcap
==32416== 
==32416== Conditional jump or move depends on uninitialised value(s)
==32416==    at 0x4C2E0F8: strlen (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==32416==    by 0x9F69B02: g_strdup (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0)
==32416==    by 0x688D331: string_fvalue_set_string (ftype-string.c:51)
==32416==    by 0x68572B1: proto_tree_add_string (proto.c:3200)
==32416==    by 0x6D572F2: dissect_ncp_request (packet-ncp2222.inc:7308)
==32416==    by 0x6D5EAC6: dissect_ncp_common (packet-ncp.c:1016)
==32416==    by 0x6D5ED0D: dissect_ncp_tcp_pdu (packet-ncp.c:1143)
==32416==    by 0x6F8E159: tcp_dissect_pdus (packet-tcp.c:2750)
==32416==    by 0x6D5DBCF: dissect_ncp_tcp (packet-ncp.c:1150)
==32416==    by 0x684353E: call_dissector_through_handle (packet.c:618)
==32416==    by 0x6843ED4: call_dissector_work (packet.c:706)
==32416==    by 0x68446CB: dissector_try_uint_new (packet.c:1163)
==32416== 
==32416== 
==32416== HEAP SUMMARY:
==32416==     in use at exit: 1,185,284 bytes in 32,567 blocks
==32416==   total heap usage: 327,204 allocs, 294,637 frees, 34,963,381 bytes
allocated
==32416== 
==32416== LEAK SUMMARY:
==32416==    definitely lost: 3,874 bytes in 159 blocks
==32416==    indirectly lost: 36,464 bytes in 49 blocks
==32416==      possibly lost: 0 bytes in 0 blocks
==32416==    still reachable: 1,144,946 bytes in 32,359 blocks
==32416==         suppressed: 0 bytes in 0 blocks
==32416== Rerun with --leak-check=full to see details of leaked memory
==32416== 
==32416== For counts of detected and suppressed errors, rerun with: -v
==32416== Use --track-origins=yes to see where uninitialised values come from
==32416== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

[ no debug trace ]

---

      You are receiving this mail because:

• You are watching all bug changes.