| Bug ID |
9659
|
| Summary |
Buildbot crash output: fuzz-2014-01-18-4301.pcap
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
http://www.wireshark.org/download/automated/captures/fuzz-2014-01-18-4301.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-01-18-4301.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/10052-wireshark_vs_omnipeek.jpg
Build host information:
Linux wsbb04 3.2.0-58-generic #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013 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=https://code.wireshark.org/review/wireshark
BUILDBOT_BUILDNUMBER=2509
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang-Code-Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=2a21b01fbbc4c98acf0a02ef9a923d648110eb99
Return value: 2
Dissector bug: 0
Valgrind error count: 0
Git commit
commit 2a21b01fbbc4c98acf0a02ef9a923d648110eb99
Author: Jörg Mayer <[email protected]>
Date: Sun Jan 19 00:48:22 2014 +0000
Add option to specify special permissions for dumpcap during cmake phase:
set(DUMPCAP_INSTALL_OPTION <val>)
where val is one of "normal" "suid" "capabilities"
Some things left to do:
- Error out in cmake if setcap isn't found or libcap isn't found.
- Move multivalue option handling into it's own macro (-file) with
value checking
svn path=/trunk/; revision=54840
Command and args: ./tshark -nVxr
tshark: The file
"/fuzz/buildbot/clangcodeanalysis/menagerie-fuzz/fuzz-2014-01-18-4301.pcap"
appears to be damaged or corrupt.
(pcapng_read_packet_block: cap_len 634477 is larger than WTAP_MAX_PACKET_SIZE
65535)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.