| Bug ID |
10732
|
| Summary |
Buildbot crash output: fuzz-2014-11-26-26546.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2014-11-26-26546.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-2014-11-26-26546.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/Assignment_1.pcap
Build host information:
Linux wsbb04 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 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=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=3072
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=449bc19ba9dd11431a3b4be547b1f37981fe77b9
Return value: 134
Dissector bug: 0
Valgrind error count: 0
Git commit
commit 449bc19ba9dd11431a3b4be547b1f37981fe77b9
Author: Martin Kaiser <[email protected]>
Date: Sat Nov 22 12:58:43 2014 +0100
Qt: support the -R option to set a read filter on the command line
rename display_filter to read_filter in some places to make it clear
what it's used for
modify MainWindow::openCaptureFile() so that a read filter can be set
when the file name is passed in cf_path, not only when it's chosen from
a file selection dialogue
don't display the read filter string in the filter toolbar
Change-Id: Ie8dc94cbd1ff7e61ce1e2a55518a28297daa5d51
Reviewed-on: https://code.wireshark.org/review/5446
Reviewed-by: Alexis La Goutte <[email protected]>
Command and args:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nVxr
**
ERROR:wmem_allocator_strict.c:77:wmem_strict_block_check_canaries: assertion
failed: (canary[i] == WMEM_CANARY_VALUE)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.