Wireshark-bugs: [Wireshark-bugs] [Bug 9968] New: Buildbot crash output: fuzz-2014-04-09-10829.pc
Date: Wed, 09 Apr 2014 20:30:37 +0000
Bug ID 9968
Summary Buildbot crash output: fuzz-2014-04-09-10829.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-09-10829.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-09-10829.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/12531-lbtru-loss-validation.pcapng.gz

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=2680
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=a653014e69a4f0e0b59393ddc03871006057b36a

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit a653014e69a4f0e0b59393ddc03871006057b36a
Author: AndersBroman <[email protected]>
Date:   Wed Apr 9 15:56:06 2014 +0200

    There seems to be some ambigiousy on how to calculate V3 checksums for
    IPv4. Introduce a preference to use the same metod as for VRRP V2.
   
http://ask.wireshark.org/questions/15291/does-wireshark-uses-a-pseudo-header-for-vrrpv3-ipv4-checksum-calculation

    Change-Id: I14bf279b0c85405c1963784737add9321d5cb7c4
    Reviewed-on: https://code.wireshark.org/review/1040
    Reviewed-by: Anders Broman <[email protected]>


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

GLib (gthread-posix.c): Unexpected error from C library during 'malloc': Cannot
allocate memory.  Aborting.

[ no debug trace ]


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