Wireshark-bugs: [Wireshark-bugs] [Bug 13181] New: Buildbot crash output: fuzz-2016-11-26-26439.p
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 26 Nov 2016 17:20:03 +0000
Bug ID 13181
Summary Buildbot crash output: fuzz-2016-11-26-26439.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-11-26-26439.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-26-26439.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/11275-cops-fuzz-test.pcap

Build host information:
Linux wsbb04 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 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=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=3798
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=d0fa82b825c15fbd9f3b6037f3d9ad4fc78d87fd

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit d0fa82b825c15fbd9f3b6037f3d9ad4fc78d87fd
Author: Gerald Combs <gerald@wireshark.org>
Date:   Fri Nov 25 11:42:26 2016 -0600

    Qt: Clean up the byte view hover highlight.

    Rename the text highlight enum "HighlightMode" to make its use and
    intent more clear. Add a mode for the offset highlight instead of using
    a separate variable. Use our palette to draw the hover highlight colors.
    Add a note about colors to the Developer's Guide.

    Change-Id: I488b2512a5058e17eb5b49c8ac55616100f32fbc
    Reviewed-on: https://code.wireshark.org/review/18953
    Petri-Dish: Gerald Combs <gerald@wireshark.org>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Gerald Combs <gerald@wireshark.org>


==18307== Memcheck, a memory error detector
==18307== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==18307== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==18307== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-11-26-26439.pcap
==18307== 
==18307== Conditional jump or move depends on uninitialised value(s)
==18307==    at 0x6B9C414: dissect_cops_pdu (packet-cops.c:1102)
==18307==    by 0x718E185: tcp_dissect_pdus (packet-tcp.c:3468)
==18307==    by 0x6B9ADE1: dissect_cops (packet-cops.c:1134)
==18307==    by 0x69AC8D5: call_dissector_through_handle (packet.c:650)
==18307==    by 0x69AC8D5: call_dissector_work (packet.c:725)
==18307==    by 0x69AC79E: dissector_try_uint_new (packet.c:1290)
==18307==    by 0x718E69F: decode_tcp_ports (packet-tcp.c:5420)
==18307==    by 0x718F9BF: process_tcp_payload (packet-tcp.c:5483)
==18307==    by 0x718EF18: desegment_tcp (packet-tcp.c:2990)
==18307==    by 0x718EF18: dissect_tcp_payload (packet-tcp.c:5550)
==18307==    by 0x7193987: dissect_tcp (packet-tcp.c:6434)
==18307==    by 0x69AC8D5: call_dissector_through_handle (packet.c:650)
==18307==    by 0x69AC8D5: call_dissector_work (packet.c:725)
==18307==    by 0x69AC79E: dissector_try_uint_new (packet.c:1290)
==18307==    by 0x6DDD452: ip_try_dissect (packet-ip.c:1978)
==18307==    by 0x6DDD452: dissect_ip_v4 (packet-ip.c:2441)
==18307== 
==18307== 
==18307== HEAP SUMMARY:
==18307==     in use at exit: 6,085,088 bytes in 9,728 blocks
==18307==   total heap usage: 265,869 allocs, 256,141 frees, 37,337,043 bytes
allocated
==18307== 
==18307== LEAK SUMMARY:
==18307==    definitely lost: 408 bytes in 88 blocks
==18307==    indirectly lost: 256 bytes in 2 blocks
==18307==      possibly lost: 0 bytes in 0 blocks
==18307==    still reachable: 6,084,424 bytes in 9,638 blocks
==18307==         suppressed: 0 bytes in 0 blocks
==18307== Rerun with --leak-check=full to see details of leaked memory
==18307== 
==18307== For counts of detected and suppressed errors, rerun with: -v
==18307== Use --track-origins=yes to see where uninitialised values come from
==18307== 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.