We're now a non-profit! Support open source packet analysis by making a donation.

Wireshark-bugs: [Wireshark-bugs] [Bug 9987] New: Buildbot crash output: fuzz-2014-04-12-23527.pc

Date: Sun, 13 Apr 2014 17:00:03 +0000
Bug ID 9987
Summary Buildbot crash output: fuzz-2014-04-12-23527.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-04-12-23527.pcap
OS Ubuntu
Severity Major
Priority High
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Problems have been found with the following capture file:


Input file: /home/wireshark/menagerie/menagerie/11958-table_feats.pcap

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

Return value:  134

Dissector bug:  0

Valgrind error count:  0

Git commit
commit cb16dff992c3844936bf5829f19e5a5247458503
Author: Guy Harris <[email protected]>
Date:   Sat Apr 12 15:26:34 2014 -0700

    Get rid of more tvb_get_nstringz* calls.

    Add an FT_STRINGZPAD type, for null-padded strings (typically
    fixed-length fields, where the string can be up to the length of the
    field, and is null-padded if it's shorter than that), and use it.  Use
    IS_FT_STRING() in more cases, so that less code needs to know what types
    are string types.

    Add a tvb_get_stringzpad() routine, which gets null-padded strings.
    Currently, it does the same thing that tvb_get_string_enc() does, but
    that might change if we don't store string values as null-terminated

    Change-Id: I46f56e130de8f419a19b56ded914e24cc7518a66
    Reviewed-on: https://code.wireshark.org/review/1082
    Reviewed-by: Guy Harris <[email protected]>

Command and args:

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

[ no debug trace ]

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