Wireshark-bugs: [Wireshark-bugs] [Bug 12721] New: Buildbot crash output: fuzz-2016-08-08-25049.p
Date: Mon, 08 Aug 2016 08:10:05 +0000
Bug ID 12721
Summary Buildbot crash output: fuzz-2016-08-08-25049.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-08-08-25049.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-08-25049.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.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=29
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=bede749b7dfdc3eb417c77ef1089fcd673ac2026

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit bede749b7dfdc3eb417c77ef1089fcd673ac2026
Author: Peter Wu <peter@lekensteyn.nl>
Date:   Sun Aug 7 12:58:59 2016 +0200

    prefs: fix crash with -o column.foo:x

    The gui.column module is somehow special, it has no name since it is
    part of the gui module. This causes a crash when trying to invoke
    `strcmp(module->name /* NULL */, "mgcp")`.

    Always look up prefs inside gui_column_module when the given prefs
    module is "column" instead of matching two specific names.

    Change-Id: I47e354d11b6fd01818b0627a249b506a8f9510cc
    Reviewed-on: https://code.wireshark.org/review/16937
    Petri-Dish: Peter Wu <peter@lekensteyn.nl>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Peter Wu <peter@lekensteyn.nl>
    (cherry picked from commit 1ea6b4fe2e4b6e068694301c4ffc731e2309c797)
    Reviewed-on: https://code.wireshark.org/review/16938


==25102== Memcheck, a memory error detector
==25102== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==25102== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==25102== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-08-25049.pcap
==25102== 
==25102== 
==25102== HEAP SUMMARY:
==25102==     in use at exit: 1,505,163 bytes in 39,709 blocks
==25102==   total heap usage: 264,863 allocs, 225,154 frees, 30,555,897 bytes
allocated
==25102== 
==25102== LEAK SUMMARY:
==25102==    definitely lost: 332,998 bytes in 150 blocks
==25102==    indirectly lost: 726,400 bytes in 29,964 blocks
==25102==      possibly lost: 0 bytes in 0 blocks
==25102==    still reachable: 445,765 bytes in 9,595 blocks
==25102==         suppressed: 0 bytes in 0 blocks
==25102== Rerun with --leak-check=full to see details of leaked memory
==25102== 
==25102== For counts of detected and suppressed errors, rerun with: -v
==25102== 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.