Wireshark-bugs: [Wireshark-bugs] [Bug 12992] New: Buildbot crash output: fuzz-2016-10-10-21479.p
Date: Mon, 10 Oct 2016 04:00:03 +0000
Bug ID 12992
Summary Buildbot crash output: fuzz-2016-10-10-21479.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-10-10-21479.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-10-10-21479.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/0001.txt.6

Build host information:
Linux wsbb04 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 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=clang-code-analysis
BUILDBOT_BUILDNUMBER=3737
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=dd589f5c169f0d9feb55d86d4bc3fe3b991ea822

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit dd589f5c169f0d9feb55d86d4bc3fe3b991ea822
Author: Jaap Keuter <jaap.keuter@xs4all.nl>
Date:   Tue Oct 4 19:55:12 2016 +0200

    Qt: valign text in RTP Stream Analysis window.

    The text on the left hand side of the RTP Stream Analtsis window is
    a (HTML) table of table headers followed by table data. For some reason
    the table data is center aligned in the cells of the table. This does not
    line up with the text in the table header cells.

    See http://imgur.com/a/QIQFd

    Also the HTML document is not compliant. Closing tags are missing, for
    td and html itself.

    Change-Id: I1cd58e8702db12433c863757141a6b68c1e2550c
    Reviewed-on: https://code.wireshark.org/review/18074
    Reviewed-by: Jaap Keuter <jaap.keuter@xs4all.nl>
    Petri-Dish: Jaap Keuter <jaap.keuter@xs4all.nl>
    Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
    Reviewed-by: Gerald Combs <gerald@wireshark.org>


==21794== Memcheck, a memory error detector
==21794== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==21794== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==21794== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-10-10-21479.pcap
==21794== 
==21794== 
==21794== HEAP SUMMARY:
==21794==     in use at exit: 6,012,917 bytes in 9,667 blocks
==21794==   total heap usage: 259,903 allocs, 250,236 frees, 36,959,086 bytes
allocated
==21794== 
==21794== LEAK SUMMARY:
==21794==    definitely lost: 0 bytes in 0 blocks
==21794==    indirectly lost: 0 bytes in 0 blocks
==21794==      possibly lost: 0 bytes in 0 blocks
==21794==    still reachable: 6,012,917 bytes in 9,667 blocks
==21794==         suppressed: 0 bytes in 0 blocks
==21794== Rerun with --leak-check=full to see details of leaked memory
==21794== 
==21794== For counts of detected and suppressed errors, rerun with: -v
==21794== 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.