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 12708] New: Buildbot crash output: fuzz-2016-08-04-22795.p

Date: Thu, 04 Aug 2016 05:40:05 +0000
Bug ID 12708
Summary Buildbot crash output: fuzz-2016-08-04-22795.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-08-04-22795.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-04-22795.pcap

stderr:
Input file:
/home/wireshark/menagerie/menagerie/1044-outbound-call-filtered.pcap

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=162
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.0/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=3f9ce2cac498ff2821fbe5a42f3ddc1c5f9ccdb5

Return value:  0

Dissector bug:  0

Valgrind error count:  2



Git commit
commit 3f9ce2cac498ff2821fbe5a42f3ddc1c5f9ccdb5
Author: Guy Harris <[email protected]>
Date:   Mon Feb 15 12:17:26 2016 -0800

    Allow test of the -D and -L options to succeed or fail with a permissions
error.

    We cannot easily predict what will happen, given the configuration of
    the OS, the permissions on files, the availability of extcap devices,
    the version of libpcap/WinPcap/NPcap (present or future), etc., etc.,
    etc..  Allow those tests to succeed (as would be the case if you have
    the necessary permissions) or fail with a non-command-line-syntax error
    (as would be the case if you don't have the necessary permissions), but
    not to fail with a command-line syntax error.

    Change-Id: I76af898d5f146fcf3507c06f101acb578085e6fa
    Reviewed-on: https://code.wireshark.org/review/13957
    Reviewed-by: Guy Harris <[email protected]>
    Reviewed-on: https://code.wireshark.org/review/16848


Command and args: ./tools/valgrind-wireshark.sh 

==3806== Memcheck, a memory error detector
==3806== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3806== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==3806== Command:
/home/wireshark/builders/wireshark-2.0-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.0/fuzz-2016-08-04-22795.pcap
==3806== 
==3806== Source and destination overlap in mempcpy(0x9cf6db6, 0x9cf6da8, 23)
==3806==    at 0x4C3500D: __GI_mempcpy (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3806==    by 0xAC8A5FD: _IO_default_xsputn (genops.c:438)
==3806==    by 0xAC5D4CA: vfprintf (vfprintf.c:1632)
==3806==    by 0xAD24FD5: __vsnprintf_chk (vsnprintf_chk.c:63)
==3806==    by 0xA009CAE: g_snprintf (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.1)
==3806==    by 0x711DBD3: dissect_h225_Alerting_UUIE (h225.cnf:422)
==3806==    by 0x6E0086D: dissect_per_choice (packet-per.c:1722)
==3806==    by 0x711C8B7: dissect_h225_T_h323_message_body (h225.cnf:245)
==3806==    by 0x6E00C1F: dissect_per_sequence (packet-per.c:1874)
==3806==    by 0x711A097: dissect_h225_H323_UU_PDU (h225.cnf:645)
==3806==    by 0x6E00C1F: dissect_per_sequence (packet-per.c:1874)
==3806==    by 0x711DF11: dissect_h225_H323_UserInformation (h225.cnf:685)
==3806==    by 0x711DF11: dissect_H323_UserInformation_PDU (h225.cnf:310)
==3806==    by 0x711DF11: dissect_h225_H323UserInformation
(packet-h225-template.c:390)
==3806== 
==3806== 
==3806== HEAP SUMMARY:
==3806==     in use at exit: 1,035,078 bytes in 28,301 blocks
==3806==   total heap usage: 391,710 allocs, 363,409 frees, 36,180,419 bytes
allocated
==3806== 
==3806== LEAK SUMMARY:
==3806==    definitely lost: 2,988 bytes in 130 blocks
==3806==    indirectly lost: 36,464 bytes in 49 blocks
==3806==      possibly lost: 0 bytes in 0 blocks
==3806==    still reachable: 995,626 bytes in 28,122 blocks
==3806==         suppressed: 0 bytes in 0 blocks
==3806== Rerun with --leak-check=full to see details of leaked memory
==3806== 
==3806== For counts of detected and suppressed errors, rerun with: -v
==3806== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 1 from 1)

[ no debug trace ]


You are receiving this mail because:
  • You are watching all bug changes.