Wireshark-bugs: [Wireshark-bugs] [Bug 10035] New: Buildbot crash output: fuzz-2014-04-23-873.pca
Date: Thu, 24 Apr 2014 07:20:03 +0000
Bug ID 10035
Summary Buildbot crash output: fuzz-2014-04-23-873.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-23-873.pcap
OS Ubuntu
Status CONFIRMED
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Problems have been found with the following capture file:

http://www.wireshark.org/download/automated/captures/fuzz-2014-04-23-873.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/nam.enc

Build host information:
Linux wsbb04 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 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=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2716
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=bf1f30b63adac4e1a39a7f0af601789c7755bd64

Return value:  133

Dissector bug:  0

Valgrind error count:  0



Git commit
commit bf1f30b63adac4e1a39a7f0af601789c7755bd64
Author: Evan Huus <[email protected]>
Date:   Wed Apr 23 16:10:51 2014 -0400

    JXTA: ask for one more segment, not one more byte

    Otherwise we end up doing reassembly of long messages one painful byte at a
time
    even when all of those bytes are in the same TCP payload. This results in
    ridiculous memory usage.

    Change-Id: Ie28d5ade1fec54e6ebc225341582270651d7371c
    Closes-Bug: 10018
    Reviewed-on: https://code.wireshark.org/review/1312
    Reviewed-by: Evan Huus <[email protected]>


Command and args:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-nVxr


(process:24460): GLib-ERROR **: /build/buildd/glib2.0-2.32.4/./glib/gmem.c:165:
failed to allocate 2661195422 bytes

[ no debug trace ]


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