https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14504

            Bug ID: 14504
           Summary: Buildbot crash output: fuzz-2018-03-08-6717.pcap
           Product: Wireshark
           Version: unspecified
          Hardware: x86-64
                OS: Ubuntu
            Status: CONFIRMED
          Severity: Major
          Priority: High
         Component: Dissection engine (libwireshark)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: buildbot-do-not-re...@wireshark.org
  Target Milestone: ---

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2018-03-08-6717.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.cap

Build host information:
Linux wsbb04 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.4 LTS
Release:        16.04
Codename:       xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=4660
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=695fbb9be0122e280755c11b9e0b89e9e256875b

Return value:  0

Dissector bug:  0

Valgrind error count:  0



Git commit
commit 695fbb9be0122e280755c11b9e0b89e9e256875b
Author: Guy Harris <g...@alum.mit.edu>
Date:   Wed Mar 7 20:09:21 2018 -0800

    Squelch some casting-away-constness warnings.

    In true_false_string_from_table(), keep the pointers to the "true" and
    "false" strings in local non-const pointer variables, so we can free
    them without a complaint.

    Only when we're finished, and have valid "true" and "false" strings, do
    we allocate the true_false_string structure and fill it in with those
    pointers.

    Change-Id: I6eb3ee46bdc47bf42d6e913c72884f0eac22997e
    Reviewed-on: https://code.wireshark.org/review/26353
    Reviewed-by: Guy Harris <g...@alum.mit.edu>



[ no debug trace ]

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to