Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12756] New: Buildbot crash output: fuzz-2016-08-17-23119.pcap

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	12756
Summary	Buildbot crash output: fuzz-2016-08-17-23119.pcap
Product	Wireshark
Version	unspecified
Hardware	x86-64
URL	https://www.wireshark.org/download/automated/captures/fuzz-2016-08-17-23119.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:

https://www.wireshark.org/download/automated/captures/fuzz-2016-08-17-23119.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/10484-frame31.cap

Build host information:
Linux wsbb04 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:    16.04
Codename:    xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-buildbot@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=41
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=d7620ff844ca3a9d2c4626fc10a4b2f1a9cb92c2

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit d7620ff844ca3a9d2c4626fc10a4b2f1a9cb92c2
Author: Peter Wu <peter@lekensteyn.nl>
Date:   Wed Aug 10 23:41:37 2016 +0200

    make-version.pl: make it work with git worktrees

    When using git worktrees, the .git file is a regular file pointing to
    the original git repository. Accept this case too. Also ignore the fact
    that the original repo could be a git-svn repo, that is very unlikely.

    Example workflow (requires git 2.5):

        # Assume work in progress in current tree. Goal is to quickly do a
        # fix in another branch and publish the changes without interfering
        # with the WIP and without marking all files out of date (which
        # slows down re-compilation).
        git worktree add /tmp/wireshark-2.2 master-2.2
        pushd /tmp/wireshark-2.2        # go to temporary tree
        git cherry-pick -x COMMIT       # backport the fix
        git review                      # submit for review
        popd                            # go back to original tree
        rm -rf /tmp/wireshark-2.2 && git worktree prune     # cleanup
        # now continue working where you left work

    Change-Id: Iba3c723142d9cbd8b07e76647594b5699ecafc67
    Reviewed-on: https://code.wireshark.org/review/17002
    Reviewed-by: Jaap Keuter <jaap.keuter@xs4all.nl>
    Petri-Dish: Jaap Keuter <jaap.keuter@xs4all.nl>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Michael Mann <mmann78@netscape.net>
    (cherry picked from commit 94c4329b8a0f64805e432af9ae89b7d624437a08)
    Reviewed-on: https://code.wireshark.org/review/17074
    Reviewed-by: Peter Wu <peter@lekensteyn.nl>


==11197== Memcheck, a memory error detector
==11197== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==11197== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==11197== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-17-23119.pcap
==11197== 
==11197== 
==11197== HEAP SUMMARY:
==11197==     in use at exit: 858,625 bytes in 26,971 blocks
==11197==   total heap usage: 294,723 allocs, 267,752 frees, 36,322,496 bytes
allocated
==11197== 
==11197== LEAK SUMMARY:
==11197==    definitely lost: 3,391 bytes in 151 blocks
==11197==    indirectly lost: 405,530 bytes in 17,121 blocks
==11197==      possibly lost: 0 bytes in 0 blocks
==11197==    still reachable: 449,704 bytes in 9,699 blocks
==11197==         suppressed: 0 bytes in 0 blocks
==11197== Rerun with --leak-check=full to see details of leaked memory
==11197== 
==11197== For counts of detected and suppressed errors, rerun with: -v
==11197== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)

[ no debug trace ]

---

      You are receiving this mail because:

• You are watching all bug changes.