Wireshark-bugs: [Wireshark-bugs] [Bug 12666] New: Buildbot crash output: fuzz-2016-07-25-2811.pc
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 25 Jul 2016 14:50:03 +0000
Bug ID 12666
Summary Buildbot crash output: fuzz-2016-07-25-2811.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-07-25-2811.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-07-25-2811.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.cap

Build host information:
Linux wsbb04 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:26 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=7
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=179d2a5d675ef2cd40c407e73337d7be0fb706ab

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 179d2a5d675ef2cd40c407e73337d7be0fb706ab
Author: Martin Kaiser <wireshark@kaiser.cx>
Date:   Sun Jul 24 18:43:14 2016 +0200

    zvt: use a hash table for the bitmaps

    table entries contain the length (if known and constant) and a function
    to dissect the payload

    this should clean up the code for bitmap dissection and make it easier
    to add new entries

    Change-Id: Id0ef5ff9e53c82171789c8a3352e56d3997d82b9
    Reviewed-on: https://code.wireshark.org/review/16632
    Petri-Dish: Martin Kaiser <wireshark@kaiser.cx>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Martin Kaiser <wireshark@kaiser.cx>
    (cherry picked from commit 688d055acd523e645c1e87267dcf4a0a9867adbd)
    Reviewed-on: https://code.wireshark.org/review/16638


==2856== Memcheck, a memory error detector
==2856== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==2856== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==2856== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-07-25-2811.pcap
==2856== 
==2856== 
==2856== HEAP SUMMARY:
==2856==     in use at exit: 1,511,355 bytes in 39,707 blocks
==2856==   total heap usage: 264,414 allocs, 224,707 frees, 30,410,854 bytes
allocated
==2856== 
==2856== LEAK SUMMARY:
==2856==    definitely lost: 332,918 bytes in 148 blocks
==2856==    indirectly lost: 725,054 bytes in 29,919 blocks
==2856==      possibly lost: 0 bytes in 0 blocks
==2856==    still reachable: 453,383 bytes in 9,640 blocks
==2856==         suppressed: 0 bytes in 0 blocks
==2856== Rerun with --leak-check=full to see details of leaked memory
==2856== 
==2856== For counts of detected and suppressed errors, rerun with: -v
==2856== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

[ no debug trace ]

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