Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 12735] New: Buildbot crash output: fuzz-2016-08-11-31587.p

Date: Thu, 11 Aug 2016 22:00:03 +0000
Bug ID 12735
Summary Buildbot crash output: fuzz-2016-08-11-31587.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-08-11-31587.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:

https://www.wireshark.org/download/automated/captures/fuzz-2016-08-11-31587.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://[email protected]:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=34
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=291e6d2ba819e029aae108dbdc4f1d14f8d1417e

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 291e6d2ba819e029aae108dbdc4f1d14f8d1417e
Author: Peter Wu <[email protected]>
Date:   Mon Aug 8 23:43:24 2016 +0200

    qnet6: fix display of MAC addresses and avoid overflow

    The MAC address is binary data, do not use tvb_get_string_enc since it
    substituted some bytes by a Unicode replacement character. Use FT_ETHER
    instead of FT_STRING to fix the display.

    Bug: 11850
    Change-Id: I3f02cfa13e8fccc18a199e4e293580c183eeddd1
    Reviewed-on: https://code.wireshark.org/review/16965
    Petri-Dish: Peter Wu <[email protected]>
    Tested-by: Petri Dish Buildbot <[email protected]>
    Reviewed-by: Pascal Quantin <[email protected]>
    Reviewed-by: Anders Broman <[email protected]>
    (cherry picked from commit 1396f6ad555178f6b81cc1a65f9cb37b2d99aebf)
    Reviewed-on: https://code.wireshark.org/review/17000
    Reviewed-by: Peter Wu <[email protected]>


==31617== Memcheck, a memory error detector
==31617== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==31617== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==31617== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-11-31587.pcap
==31617== 
==31617== 
==31617== HEAP SUMMARY:
==31617==     in use at exit: 1,506,347 bytes in 39,767 blocks
==31617==   total heap usage: 265,048 allocs, 225,281 frees, 30,555,863 bytes
allocated
==31617== 
==31617== LEAK SUMMARY:
==31617==    definitely lost: 332,998 bytes in 150 blocks
==31617==    indirectly lost: 727,840 bytes in 30,024 blocks
==31617==      possibly lost: 0 bytes in 0 blocks
==31617==    still reachable: 445,509 bytes in 9,593 blocks
==31617==         suppressed: 0 bytes in 0 blocks
==31617== Rerun with --leak-check=full to see details of leaked memory
==31617== 
==31617== For counts of detected and suppressed errors, rerun with: -v
==31617== 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.