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

stderr:
Input file: /home/wireshark/menagerie/menagerie/10484-frame31.cap

Build host information:
Linux wsbb04 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 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=fuzz-test
BUILDBOT_BUILDNUMBER=66
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=7968175e72278a34a6997321c5a25e7d32b3b823

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 7968175e72278a34a6997321c5a25e7d32b3b823
Author: Peter Wu <peter@lekensteyn.nl>
Date:   Tue Aug 30 11:12:44 2016 +0200

    time_util: fix -Wshadow issue

    time_util.c was already fixed, but the header was missing the change,
    breaking the build on a very old compiler.

    Change-Id: I95685c9a3e25dcb7567f2551b92f20c8792a6e47
    Reviewed-on: https://code.wireshark.org/review/17384
    Petri-Dish: Dario Lombardo <lomato@gmail.com>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Dario Lombardo <lomato@gmail.com>
    Reviewed-by: Peter Wu <peter@lekensteyn.nl>
    (cherry picked from commit a892c90367a9f1b1d3d962cfe958174b8fefcaee)
    Reviewed-on: https://code.wireshark.org/review/17390


==23936== Memcheck, a memory error detector
==23936== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==23936== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==23936== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-30-29171.pcap
==23936== 
==23936== 
==23936== HEAP SUMMARY:
==23936==     in use at exit: 858,619 bytes in 26,971 blocks
==23936==   total heap usage: 297,357 allocs, 270,386 frees, 36,494,568 bytes
allocated
==23936== 
==23936== LEAK SUMMARY:
==23936==    definitely lost: 3,391 bytes in 151 blocks
==23936==    indirectly lost: 405,530 bytes in 17,121 blocks
==23936==      possibly lost: 0 bytes in 0 blocks
==23936==    still reachable: 449,698 bytes in 9,699 blocks
==23936==         suppressed: 0 bytes in 0 blocks
==23936== Rerun with --leak-check=full to see details of leaked memory
==23936== 
==23936== For counts of detected and suppressed errors, rerun with: -v
==23936== 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.