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 9928] New: Buildbot crash output: fuzz-2014-03-27-27165.pc

Date: Thu, 27 Mar 2014 13:20:04 +0000
Bug ID 9928
Summary Buildbot crash output: fuzz-2014-03-27-27165.pcap
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86-64
URL http://www.wireshark.org/download/automated/captures/fuzz-2014-03-27-27165.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:

http://www.wireshark.org/download/automated/captures/fuzz-2014-03-27-27165.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/10860-packet-gsm.pcap

Build host information:
Linux wsbb04 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 12.04.4 LTS
Release:    12.04
Codename:    precise

Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2658
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=a99a0360c47c689abdf1ef09e09dea02749824d2

Return value:  134

Dissector bug:  0

Valgrind error count:  0



Git commit
commit a99a0360c47c689abdf1ef09e09dea02749824d2
Author: Michal Labedzki <[email protected]>
Date:   Mon Mar 24 11:54:00 2014 +0100

    Bluetooth: Fix wrong recognized RFCOMM services

    It seems that RFCOMM service can be dynamically changed while
    connection is still alive. In other words: host can connect to
    remote device and set one RFCOMM service (remote service), but later
    remote device can change service to one of host service without
    any disconnection. This patch add support for this case.
    Also improve searching for useful UUID service through SDP.

    Change-Id: I9e03b9b965d6b0d9761b4a451cdeb4a1a33ca017
    Reviewed-on: https://code.wireshark.org/review/808
    Reviewed-by: Anders Broman <[email protected]>


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

==30770== Memcheck, a memory error detector
==30770== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==30770== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==30770== Command:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2014-03-27-27165.pcap
==30770== 
**
ERROR:packet.c:2246:call_dissector_only: assertion failed: (handle != NULL)
==30770== 
==30770== HEAP SUMMARY:
==30770==     in use at exit: 18,488,540 bytes in 479,622 blocks
==30770==   total heap usage: 943,914 allocs, 464,292 frees, 51,323,457 bytes
allocated
==30770== 
==30770== LEAK SUMMARY:
==30770==    definitely lost: 2,079 bytes in 27 blocks
==30770==    indirectly lost: 8 bytes in 1 blocks
==30770==      possibly lost: 0 bytes in 0 blocks
==30770==    still reachable: 18,486,453 bytes in 479,594 blocks
==30770==         suppressed: 0 bytes in 0 blocks
==30770== Rerun with --leak-check=full to see details of leaked memory
==30770== 
==30770== For counts of detected and suppressed errors, rerun with: -v
==30770== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 3)
./tools/valgrind-wireshark.sh: line 107: 30770 Aborted                 (core
dumped) $LIBTOOL valgrind --suppressions=`dirname $0`/vg-suppressions
--tool=$TOOL $CALLGRIND_OUT_FILE $VERBOSE $LEAK_CHECK $REACHABLE $TRACK_ORIGINS
$COMMAND $COMMAND_ARGS $PCAP $COMMAND_ARGS2 > /dev/null

[ no debug trace ]


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