Bug ID |
12775
|
Summary |
Buildbot crash output: fuzz-2016-08-22-26004.pcap
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-08-22-26004.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-22-26004.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/10484-frame31.cap
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=47
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=b6f7d7379847c430e24b9410761c31946485d0a8
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit b6f7d7379847c430e24b9410761c31946485d0a8
Author: Pascal Quantin <[email protected]>
Date: Sat Aug 20 21:03:02 2016 +0200
COAP: ensure that key_token is always initialized
Even when the token length is 0.
Bug: 12771
Change-Id: I0d77f0411fe90a6702d1f23ba9cd4b61433a5995
Reviewed-on: https://code.wireshark.org/review/17194
Reviewed-by: Pascal Quantin <[email protected]>
Petri-Dish: Pascal Quantin <[email protected]>
Tested-by: Petri Dish Buildbot <[email protected]>
Reviewed-by: Anders Broman <[email protected]>
(cherry picked from commit 0a9e84264947c75bbe96d0b67cb2dbe0f521f3b8)
Reviewed-on: https://code.wireshark.org/review/17196
==15962== Memcheck, a memory error detector
==15962== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==15962== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==15962== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-08-22-26004.pcap
==15962==
==15962==
==15962== HEAP SUMMARY:
==15962== in use at exit: 858,873 bytes in 26,970 blocks
==15962== total heap usage: 294,742 allocs, 267,772 frees, 36,340,404 bytes
allocated
==15962==
==15962== LEAK SUMMARY:
==15962== definitely lost: 3,367 bytes in 150 blocks
==15962== indirectly lost: 405,530 bytes in 17,121 blocks
==15962== possibly lost: 0 bytes in 0 blocks
==15962== still reachable: 449,976 bytes in 9,699 blocks
==15962== suppressed: 0 bytes in 0 blocks
==15962== Rerun with --leak-check=full to see details of leaked memory
==15962==
==15962== For counts of detected and suppressed errors, rerun with: -v
==15962== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.