https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13219

            Bug ID: 13219
           Summary: Buildbot crash output: fuzz-2016-12-07-9609.pcap
           Product: Wireshark
           Version: unspecified
          Hardware: x86-64
               URL: https://www.wireshark.org/download/automated/captures/
                    fuzz-2016-12-07-9609.pcap
                OS: Ubuntu
            Status: CONFIRMED
          Severity: Major
          Priority: High
         Component: Dissection engine (libwireshark)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: buildbot-do-not-re...@wireshark.org

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2016-12-07-9609.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/13651-nfsv4rdma_mount.pcap

Build host information:
Linux wsbb04 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 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-build...@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=3810
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=f39389e945e11a82905bc5b71ada85f3b90e9bab

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit f39389e945e11a82905bc5b71ada85f3b90e9bab
Author: Chuck Lever <chuck.le...@oracle.com>
Date:   Tue Dec 6 11:25:59 2016 -0500

    packet-rpcrdma: Fix selection size in chunk list dissectors

    Use proto_item_set_len instead of walking the packet ahead of time
    trying to compute the size.

    Change-Id: I5eb3da1fef45895853cb5b6b198d0310394e4176
    Signed-off-by: Chuck Lever <chuck.le...@oracle.com>
    Reviewed-on: https://code.wireshark.org/review/19120
    Reviewed-by: Michael Mann <mman...@netscape.net>
    Petri-Dish: Michael Mann <mman...@netscape.net>
    Tested-by: Petri Dish Buildbot <buildbot-no-re...@wireshark.org>
    Reviewed-by: Anders Broman <a.broma...@gmail.com>


==18459== Memcheck, a memory error detector
==18459== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==18459== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==18459== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-12-07-9609.pcap
==18459== 
==18459== Invalid read of size 2
==18459==    at 0x69977C1: ib_addr_to_str (address_types.c:451)
==18459==    by 0x699FF8C: col_set_addr (column-utils.c:1913)
==18459==    by 0x699FE77: col_fill_in (column-utils.c:2180)
==18459==    by 0x416797: print_packet (tshark.c:3852)
==18459==    by 0x416389: process_packet (tshark.c:3492)
==18459==    by 0x4140D1: load_cap_file (tshark.c:3234)
==18459==    by 0x4140D1: main (tshark.c:1934)
==18459==  Address 0xffefff5f0 is on thread 1's stack
==18459==  2336 bytes below stack pointer
==18459== 
==18459== 
==18459== HEAP SUMMARY:
==18459==     in use at exit: 6,085,214 bytes in 9,743 blocks
==18459==   total heap usage: 266,280 allocs, 256,537 frees, 37,335,172 bytes
allocated
==18459== 
==18459== LEAK SUMMARY:
==18459==    definitely lost: 360 bytes in 87 blocks
==18459==    indirectly lost: 0 bytes in 0 blocks
==18459==      possibly lost: 0 bytes in 0 blocks
==18459==    still reachable: 6,084,854 bytes in 9,656 blocks
==18459==         suppressed: 0 bytes in 0 blocks
==18459== Rerun with --leak-check=full to see details of leaked memory
==18459== 
==18459== For counts of detected and suppressed errors, rerun with: -v
==18459== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

[ no debug trace ]

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to