Wireshark-bugs: [Wireshark-bugs] [Bug 10249] New: Buildbot crash output: fuzz-2014-07-02-14950.p
Date: Wed, 02 Jul 2014 14:40:04 +0000
Bug ID 10249
Summary Buildbot crash output: fuzz-2014-07-02-14950.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-07-02-14950.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:

http://www.wireshark.org/download/automated/captures/fuzz-2014-07-02-14950.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/5472-tight-hex.pcap

Build host information:
Linux wsbb04 3.2.0-65-generic #98-Ubuntu SMP Wed Jun 11 20:27:07 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 12.04.4 LTS
Release:    12.04
Codename:    precise

Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=69
BUILDBOT_URL=http://buildbot.wireshark.org/master-1.12/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=d57051446bec7f63cf8bcf6e7045632e3636a09f

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit d57051446bec7f63cf8bcf6e7045632e3636a09f
Author: Jeff Morriss <jeff.morriss.ws@gmail.com>
Date:   Tue Jul 1 18:28:26 2014 -0400

    Get rid of rpath when we're building RPMs.

    Fedora prohibits it, we don't need it, and it gets in the way some times.

    Change-Id: I92cee959f471866ff90efe9f96e4fa519c357dd9
    Reviewed-on: https://code.wireshark.org/review/2763
    Reviewed-by: Jeff Morriss <jeff.morriss.ws@gmail.com>
    (cherry picked from commit a4a624e4c5f16ad75ab9124e390f82efaca06512)
    Reviewed-on: https://code.wireshark.org/review/2765


Command and args:
/home/wireshark/builders/wireshark-1.12-fuzz/fuzztest/install/bin/tshark -nVxr


***MEMORY-ERROR***: [28271]: GSlice: MemChecker: failure in debugging tree:
Cannot allocate memory

[ no debug trace ]


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