Bug ID |
12690
|
Summary |
Buildbot crash output: fuzz-2016-07-29-17870.pcap
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-07-29-17870.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-07-29-17870.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_BUILDNUMBER=14
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=8c7ab5f2b2c18f23c1baa856e30ff8dcb0b7151c
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 8c7ab5f2b2c18f23c1baa856e30ff8dcb0b7151c
Author: Pascal Quantin <[email protected]>
Date: Thu Jul 28 19:56:56 2016 +0200
proto.c: do not perform bound checks in
proto_tree_add_text(_valist)_internal if tvb is NULL
As seen in bug 12676, some buggy dissectors do not systematically provide a
tvb when calling proto_tree_add_XXX functions.
On stable branch, let's deactivate the bound checks in that case.
Bug: 12676
Change-Id: Ia3cf0b0972c127f34feca2e097e0ec1fd1753b23
Reviewed-on: https://code.wireshark.org/review/16752
Petri-Dish: Pascal Quantin <[email protected]>
Tested-by: Petri Dish Buildbot <[email protected]>
Reviewed-by: Pascal Quantin <[email protected]>
==17920== Memcheck, a memory error detector
==17920== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==17920== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==17920== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-07-29-17870.pcap
==17920==
==17920==
==17920== HEAP SUMMARY:
==17920== in use at exit: 1,511,140 bytes in 39,711 blocks
==17920== total heap usage: 264,166 allocs, 224,455 frees, 30,405,258 bytes
allocated
==17920==
==17920== LEAK SUMMARY:
==17920== definitely lost: 332,918 bytes in 148 blocks
==17920== indirectly lost: 725,222 bytes in 29,926 blocks
==17920== possibly lost: 0 bytes in 0 blocks
==17920== still reachable: 453,000 bytes in 9,637 blocks
==17920== suppressed: 0 bytes in 0 blocks
==17920== Rerun with --leak-check=full to see details of leaked memory
==17920==
==17920== For counts of detected and suppressed errors, rerun with: -v
==17920== 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.