Wireshark-bugs: [Wireshark-bugs] [Bug 10634] New: Buildbot crash output: fuzz-2014-10-26-19015.p
Bug ID |
10634
|
Summary |
Buildbot crash output: fuzz-2014-10-26-19015.pcap
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
https://www.wireshark.org/download/automated/captures/fuzz-2014-10-26-19015.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-2014-10-26-19015.pcap
stderr:
Input file:
/home/wireshark/menagerie/menagerie/10648-dcp_split_00004_20130424095731
Build host information:
Linux wsbb04 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=602
BUILDBOT_URL=http://buildbot.wireshark.org/trunk-1.10/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=8f61ce9b8a4a038849af88328dfc3ed74c2591a6
Return value: 134
Dissector bug: 0
Valgrind error count: 0
Git commit
commit 8f61ce9b8a4a038849af88328dfc3ed74c2591a6
Author: Evan Huus <eapache@gmail.com>
Date: Sat Oct 25 14:08:57 2014 -0400
ncp2222: initialize buffer in build_expert_data
We do a bunch of conditional logic to fill in the buffer, and then were
checking
strlen(buffer) to see if we'd actually filled it in or not, but if we
hadn't
then the buffer was garbage and strlen(buffer) was throwing valgrind
warnings.
Ensure this works as intended by setting the first byte of the buffer
unconditionally at the beginning, so strlen(buffer) returns 0 as expected
in
that case.
Bug: 10628
Change-Id: I6f6c29fbbcb601b6ebccb3a4b312f0fa72c169ae
Reviewed-on: https://code.wireshark.org/review/4926
Reviewed-by: Evan Huus <eapache@gmail.com>
Command and args: ./tshark -nVxr
Out Of Memory!
Sorry, but TShark has to terminate now!
Some infos / workarounds can be found at:
http://wiki.wireshark.org/KnownBugs/OutOfMemory
**
ERROR:wmem_scopes.c:125:wmem_leave_file_scope: assertion failed:
(!in_packet_scope)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.