Wireshark-bugs: [Wireshark-bugs] [Bug 9822] New: Buildbot crash output: fuzz-2014-02-28-30629.pc
Date: Sat, 01 Mar 2014 16:30:03 +0000
Bug ID 9822
Summary Buildbot crash output: fuzz-2014-02-28-30629.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-02-28-30629.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-02-28-30629.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/video_call_1.pcap

Build host information:
Linux wsbb04 3.2.0-59-generic #90-Ubuntu SMP Tue Jan 7 22:43:51 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=370
BUILDBOT_URL=http://buildbot.wireshark.org/trunk-1.10/
BUILDBOT_BUILDERNAME=Fuzz-Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=d8075e79f7dc435d68b942695d3d1604f3e166b7

Return value:  133

Dissector bug:  0

Valgrind error count:  0



Git commit
commit d8075e79f7dc435d68b942695d3d1604f3e166b7
Author: Evan Huus <eapache@gmail.com>
Date:   Wed Feb 26 12:47:35 2014 -0500

    Don't mix emem and glib memory and init routines.

    The seasonal memory is freed before the init routine is called, leading to
a
    whole bunch of use-after-free errors.

    Fixes bug #9802 (and duplicates).

    This introduces a few minor leaks but I can't find an easy way to add
additional
    free calls that doesn't lead to double-free errors.

    Change-Id: Idda79cb643d46d29253165cdeefeed189db6b078
    Reviewed-on: https://code.wireshark.org/review/406
    Reviewed-by: Evan Huus <eapache@gmail.com>


Command and args: ./tshark -nVxr


** (process:26323): ERROR **: Memory corrupted

[ no debug trace ]


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