[bugzilla-daemon@xxxxxxxxxxxxx]

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

stderr:
Input file: /home/wireshark/menagerie/menagerie/before.pcap

Build host information:
Linux wsbb04 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:    16.04
Codename:    xenial

Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=3772
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=ddd1c87d43781533c3ec10279857e3870d12437e

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit ddd1c87d43781533c3ec10279857e3870d12437e
Author: Martin Kaiser <wireshark@kaiser.cx>
Date:   Sun Oct 30 19:46:56 2016 +0100

    cmake: avoid leading space in linker options

    This causes problems with cmake 2.8.9, which ships with Debian Wheezy.

    Reorder the linker options to avoid a leading space. According to GNU
    ld's manual, the order of linker options on the command line does not
    matter. This should be the same for Visual Studio's cl.exe and for
    clang's linker.

    See
    https://www.wireshark.org/lists/wireshark-dev/201604/msg00141.html
    for more details about the problem.

    Change-Id: Ieaf7425600d394f365b01747747665233693fea2
    Reviewed-on: https://code.wireshark.org/review/18581
    Petri-Dish: Martin Kaiser <wireshark@kaiser.cx>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Martin Kaiser <wireshark@kaiser.cx>


==2143== Memcheck, a memory error detector
==2143== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==2143== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==2143== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-11-10-7822.pcap
==2143== 
==2143== Conditional jump or move depends on uninitialised value(s)
==2143==    at 0x69DC906: fragment_add_seq_work (reassemble.c:1686)
==2143==    by 0x69DC906: fragment_add_seq_common (reassemble.c:1956)
==2143==    by 0x69DCCB7: fragment_add_seq_check_work (reassemble.c:2037)
==2143==    by 0x69DCC4B: fragment_add_seq_check (reassemble.c:2074)
==2143==    by 0x6FC8668: dissect_p_mul (packet-p_mul.c:1290)
==2143==    by 0x69B2285: call_dissector_through_handle (packet.c:650)
==2143==    by 0x69B2285: call_dissector_work (packet.c:725)
==2143==    by 0x69B2369: dissector_try_uint_new (packet.c:1290)
==2143==    by 0x69B2369: dissector_try_uint (packet.c:1316)
==2143==    by 0x709BADD: dissect_s5066_common (packet-s5066sis.c:1054)
==2143==    by 0x718EA75: tcp_dissect_pdus (packet-tcp.c:3266)
==2143==    by 0x709A348: dissect_s5066_tcp (packet-s5066sis.c:980)
==2143==    by 0x69B2285: call_dissector_through_handle (packet.c:650)
==2143==    by 0x69B2285: call_dissector_work (packet.c:725)
==2143==    by 0x69B214E: dissector_try_uint_new (packet.c:1290)
==2143==    by 0x718EF37: decode_tcp_ports (packet-tcp.c:5191)
==2143== 
==2143== 
==2143== HEAP SUMMARY:
==2143==     in use at exit: 6,083,296 bytes in 9,727 blocks
==2143==   total heap usage: 265,813 allocs, 256,086 frees, 37,375,530 bytes
allocated
==2143== 
==2143== LEAK SUMMARY:
==2143==    definitely lost: 608 bytes in 89 blocks
==2143==    indirectly lost: 416 bytes in 8 blocks
==2143==      possibly lost: 0 bytes in 0 blocks
==2143==    still reachable: 6,082,272 bytes in 9,630 blocks
==2143==         suppressed: 0 bytes in 0 blocks
==2143== Rerun with --leak-check=full to see details of leaked memory
==2143== 
==2143== For counts of detected and suppressed errors, rerun with: -v
==2143== Use --track-origins=yes to see where uninitialised values come from
==2143== 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.