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

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

Build host information:
Linux wsbb04 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 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=fuzz-test
BUILDBOT_BUILDNUMBER=22
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=57ab1d4023df2a2e02cd4c4b4bed26bcbf3e7d14

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 57ab1d4023df2a2e02cd4c4b4bed26bcbf3e7d14
Author: David McKay <mckay.david@gmail.com>
Date:   Mon Aug 1 22:56:45 2016 -0400

    Bugfix endian issues with 802.11 FCS

    Rather than trying to swap fields to be big-endian, just make everything
    little-endian.

    Bug: 12697
    Change-Id: I07e7fd651c4a32dba764d111b34acdf32958c195
    Reviewed-on: https://code.wireshark.org/review/16836
    Reviewed-by: Michael Mann <mmann78@netscape.net>
    Petri-Dish: Michael Mann <mmann78@netscape.net>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Anders Broman <a.broman58@gmail.com>
    (cherry picked from commit 6343e1dc67b3c99f2ac900b026ad00ee2d04b063)
    Reviewed-on: https://code.wireshark.org/review/16845


==25061== Memcheck, a memory error detector
==25061== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==25061== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==25061== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-03-25016.pcap
==25061== 
==25061== 
==25061== HEAP SUMMARY:
==25061==     in use at exit: 1,505,627 bytes in 39,708 blocks
==25061==   total heap usage: 265,040 allocs, 225,332 frees, 30,562,435 bytes
allocated
==25061== 
==25061== LEAK SUMMARY:
==25061==    definitely lost: 332,998 bytes in 150 blocks
==25061==    indirectly lost: 726,352 bytes in 29,962 blocks
==25061==      possibly lost: 0 bytes in 0 blocks
==25061==    still reachable: 446,277 bytes in 9,596 blocks
==25061==         suppressed: 0 bytes in 0 blocks
==25061== Rerun with --leak-check=full to see details of leaked memory
==25061== 
==25061== For counts of detected and suppressed errors, rerun with: -v
==25061== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)

[ no debug trace ]

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