Wireshark-bugs: [Wireshark-bugs] [Bug 13170] New: Buildbot crash output: fuzz-2016-11-23-22982.p
Date: Thu, 24 Nov 2016 00:40:03 +0000
Bug ID 13170
Summary Buildbot crash output: fuzz-2016-11-23-22982.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-11-23-22982.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-23-22982.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=3789
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=24f7b93dc12577b5d9d72ff4f3fe786b65c517a1

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 24f7b93dc12577b5d9d72ff4f3fe786b65c517a1
Author: Dario Lombardo <lomato@gmail.com>
Date:   Mon Nov 21 23:52:04 2016 +0100

    debian-setup: check for both libgnutls-dev and libgnutls28-dev.

    Change-Id: Ibe63e1d9b7527295223fc817889a60db79869e27
    Reviewed-on: https://code.wireshark.org/review/18935
    Reviewed-by: Peter Wu <peter@lekensteyn.nl>
    Reviewed-by: Dario Lombardo <lomato@gmail.com>


==3331== Memcheck, a memory error detector
==3331== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3331== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==3331== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-11-23-22982.pcap
==3331== 
==3331== Conditional jump or move depends on uninitialised value(s)
==3331==    at 0x6B9B2D4: dissect_cops_pdu (packet-cops.c:1102)
==3331==    by 0x718B345: tcp_dissect_pdus (packet-tcp.c:3468)
==3331==    by 0x6B99CA1: dissect_cops (packet-cops.c:1134)
==3331==    by 0x69AB795: call_dissector_through_handle (packet.c:650)
==3331==    by 0x69AB795: call_dissector_work (packet.c:725)
==3331==    by 0x69AB65E: dissector_try_uint_new (packet.c:1290)
==3331==    by 0x718B85F: decode_tcp_ports (packet-tcp.c:5420)
==3331==    by 0x718CB7F: process_tcp_payload (packet-tcp.c:5483)
==3331==    by 0x718C0D8: desegment_tcp (packet-tcp.c:2990)
==3331==    by 0x718C0D8: dissect_tcp_payload (packet-tcp.c:5550)
==3331==    by 0x7190B47: dissect_tcp (packet-tcp.c:6434)
==3331==    by 0x69AB795: call_dissector_through_handle (packet.c:650)
==3331==    by 0x69AB795: call_dissector_work (packet.c:725)
==3331==    by 0x69AB65E: dissector_try_uint_new (packet.c:1290)
==3331==    by 0x6DDC2D2: ip_try_dissect (packet-ip.c:1978)
==3331==    by 0x6DDC2D2: dissect_ip_v4 (packet-ip.c:2441)
==3331== 
==3331== 
==3331== HEAP SUMMARY:
==3331==     in use at exit: 6,085,296 bytes in 9,725 blocks
==3331==   total heap usage: 266,000 allocs, 256,275 frees, 37,342,939 bytes
allocated
==3331== 
==3331== LEAK SUMMARY:
==3331==    definitely lost: 408 bytes in 88 blocks
==3331==    indirectly lost: 256 bytes in 2 blocks
==3331==      possibly lost: 0 bytes in 0 blocks
==3331==    still reachable: 6,084,632 bytes in 9,635 blocks
==3331==         suppressed: 0 bytes in 0 blocks
==3331== Rerun with --leak-check=full to see details of leaked memory
==3331== 
==3331== For counts of detected and suppressed errors, rerun with: -v
==3331== Use --track-origins=yes to see where uninitialised values come from
==3331== 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.