| Bug ID |
12656
|
| Summary |
Buildbot crash output: fuzz-2016-07-24-1421.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-07-24-1421.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-24-1421.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=6
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=8e089c331e0f2e437daaa95b984d9e19d6905f1a
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 8e089c331e0f2e437daaa95b984d9e19d6905f1a
Author: Guy Harris <[email protected]>
Date: Sat Jul 23 19:16:36 2016 -0700
Enable "Save As..." iff cf_can_save_as() returns TRUE.
Currently, cf_can_save() really means "*there's something to save* and
we can write it out"; "Save As..." should be enabled even if there are
no changes to save, in case the user just wants to write the existing
file contents out to a new file and have the new file be the current
file. That matches the behavior of the GTK+ version.
(We might want to enable "Save" even if there are no changes to save;
some other programs do that, such as the TextEdit, WordPad, KWrite, and
gedit simple text editors. If so, however, we should make "Save" write
stuff out even if there are no changes to save.
Note, however, that we're a bit different from most "editors", in that
we don't read the entire file into memory - we keep the file open and
read packet data from it, because we want to be able to read files that
won't fit into memory. That *might* change what we ultimately want to
do with "Save".)
Bug: 12630
Change-Id: I8a2327b5d6ddab7c4f0367f132460b507da38577
Reviewed-on: https://code.wireshark.org/review/16612
Reviewed-by: Guy Harris <[email protected]>
(cherry picked from commit f930da87a738171f10af56a4acd7979c1469211a)
Reviewed-on: https://code.wireshark.org/review/16613
==1476== Memcheck, a memory error detector
==1476== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==1476== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==1476== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-07-24-1421.pcap
==1476==
==1476==
==1476== HEAP SUMMARY:
==1476== in use at exit: 1,509,483 bytes in 39,664 blocks
==1476== total heap usage: 264,470 allocs, 224,806 frees, 30,432,117 bytes
allocated
==1476==
==1476== LEAK SUMMARY:
==1476== definitely lost: 332,918 bytes in 148 blocks
==1476== indirectly lost: 724,166 bytes in 29,882 blocks
==1476== possibly lost: 0 bytes in 0 blocks
==1476== still reachable: 452,399 bytes in 9,634 blocks
==1476== suppressed: 0 bytes in 0 blocks
==1476== Rerun with --leak-check=full to see details of leaked memory
==1476==
==1476== For counts of detected and suppressed errors, rerun with: -v
==1476== 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.