Wireshark-bugs: [Wireshark-bugs] [Bug 12698] New: Buildbot crash output: fuzz-2016-08-01-28032.p

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 01 Aug 2016 19:00:02 +0000
Bug ID 12698
Summary Buildbot crash output: fuzz-2016-08-01-28032.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-08-01-28032.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-01-28032.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.cap

Build host information:
Linux wsbb04 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=18
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=1c9e52ea093625055d66c9ec7a413a93a09ee441

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 1c9e52ea093625055d66c9ec7a413a93a09ee441
Author: Vasil Velichckov <[email protected]>
Date:   Sun Jul 31 16:59:01 2016 +0300

    BER: Fix segmentation fault when configuring new OIDs

     Program terminated with signal 11, Segmentation fault.
     #0  0x00007f573e5bdecf in uat_fld_chk_oid (u1=0x2eb1830,
strptr=0x7f573c8431e4 "", len=0, u2=0x0, u3=0x0, err=0x7ffee1668748) at
uat.c:494
     494        if(strptr[len-1] == '.') {
     (gdb)
     (gdb) bt
     #0  0x00007f573e5bdecf in uat_fld_chk_oid (u1=0x2eb1830,
strptr=0x7f573c8431e4 "", len=0, u2=0x0, u3=0x0, err=0x7ffee1668748) at
uat.c:494
     #1  0x0000000000485dfc in uat_dlg_cb (win=0x3844290, user_data=0x3632bc0)
at uat_gui.c:364
     #2  0x00007f573b2f19a7 in _g_closure_invoke_va (closure=0x3367130,
return_value=0x0, instance=0x3844290, args=0x7ffee1668a78, n_params=0,

    Change-Id: Ic61480f8c1f2cd833c58de0b2acc24dcb831578f
    Reviewed-on: https://code.wireshark.org/review/16800
    Reviewed-by: Michael Mann <[email protected]>
    Petri-Dish: Michael Mann <[email protected]>
    Tested-by: Petri Dish Buildbot <[email protected]>
    Reviewed-by: Stig Bjørlykke <[email protected]>
    (cherry picked from commit bf123efe154dfdde06ee3c78cf8af05ed01a691b)
    Reviewed-on: https://code.wireshark.org/review/16814


==28098== Memcheck, a memory error detector
==28098== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==28098== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==28098== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-01-28032.pcap
==28098== 
==28098== 
==28098== HEAP SUMMARY:
==28098==     in use at exit: 1,512,292 bytes in 39,746 blocks
==28098==   total heap usage: 264,366 allocs, 224,620 frees, 30,425,162 bytes
allocated
==28098== 
==28098== LEAK SUMMARY:
==28098==    definitely lost: 332,918 bytes in 148 blocks
==28098==    indirectly lost: 725,966 bytes in 29,957 blocks
==28098==      possibly lost: 24 bytes in 1 blocks
==28098==    still reachable: 453,384 bytes in 9,640 blocks
==28098==         suppressed: 0 bytes in 0 blocks
==28098== Rerun with --leak-check=full to see details of leaked memory
==28098== 
==28098== For counts of detected and suppressed errors, rerun with: -v
==28098== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

[ no debug trace ]

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