Wireshark-bugs: [Wireshark-bugs] [Bug 12815] New: Buildbot crash output: fuzz-2016-09-02-10568.p
Date: Fri, 02 Sep 2016 02:30:03 +0000
Bug ID 12815
Summary Buildbot crash output: fuzz-2016-09-02-10568.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-09-02-10568.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-09-02-10568.pcap

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

Build host information:
Linux wsbb04 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 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=71
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=b348c388d445a32916b81ac18dea314acde7853b

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit b348c388d445a32916b81ac18dea314acde7853b
Author: Peter Wu <peter@lekensteyn.nl>
Date:   Wed Aug 31 11:11:56 2016 +0200

    gtk: fix 32-bit build

    32-bit glib before 2.31.2 expand GUINT_TO_POINTER(x) as (gpointer)x.
    add explicit cast since curr_layer_num is 8 bits. Fixes
    v1.99.10rc0-179-g1d7bcb2.

    Storing a 64-bit integer into a 32-bit pointer makes the compiler
    complain. Add explicit cast. Fixes v1.99.1rc0-76-ged0b19b.

    Change-Id: I75fdf17882a0f5ddce7d3b3e74b1bf80ff6cd4ae
    Reviewed-on: https://code.wireshark.org/review/17417
    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 e3c3d7a4afeeb8bc0519717e6c85c038fb99170a)
    Reviewed-on: https://code.wireshark.org/review/17435


==8160== Memcheck, a memory error detector
==8160== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==8160== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==8160== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-09-02-10568.pcap
==8160== 
==8160== 
==8160== HEAP SUMMARY:
==8160==     in use at exit: 858,875 bytes in 26,971 blocks
==8160==   total heap usage: 289,282 allocs, 262,311 frees, 36,352,329 bytes
allocated
==8160== 
==8160== LEAK SUMMARY:
==8160==    definitely lost: 3,367 bytes in 150 blocks
==8160==    indirectly lost: 405,530 bytes in 17,121 blocks
==8160==      possibly lost: 0 bytes in 0 blocks
==8160==    still reachable: 449,978 bytes in 9,700 blocks
==8160==         suppressed: 0 bytes in 0 blocks
==8160== Rerun with --leak-check=full to see details of leaked memory
==8160== 
==8160== For counts of detected and suppressed errors, rerun with: -v
==8160== 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.