Bug ID |
12813
|
Summary |
Buildbot crash output: fuzz-2016-09-01-30861.pcap
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-09-01-30861.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-09-01-30861.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/10484-frame31.cap
Build host information:
Linux wsbb04 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=70
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=60649ac3a4723f7d22c809a6c7cdd85ebfef94a6
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 60649ac3a4723f7d22c809a6c7cdd85ebfef94a6
Author: Peter Wu <[email protected]>
Date: Tue Aug 30 19:24:15 2016 +0200
erf: fix build against older glib
Commit v2.1.0rc0-2561-g3db7b1e started using g_int64_equal which does
not exist before glib 2.22. Note that master requires 2.22 and does not
need this fix.
Change-Id: Ie89432a6cd688b89dd346ce5cdecf96a76e92692
Reviewed-on: https://code.wireshark.org/review/17395
Reviewed-by: João Valverde <[email protected]>
Reviewed-by: Peter Wu <[email protected]>
==16474== Memcheck, a memory error detector
==16474== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==16474== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==16474== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-09-01-30861.pcap
==16474==
==16474==
==16474== HEAP SUMMARY:
==16474== in use at exit: 858,619 bytes in 26,971 blocks
==16474== total heap usage: 289,275 allocs, 262,304 frees, 36,351,528 bytes
allocated
==16474==
==16474== LEAK SUMMARY:
==16474== definitely lost: 3,367 bytes in 150 blocks
==16474== indirectly lost: 405,530 bytes in 17,121 blocks
==16474== possibly lost: 0 bytes in 0 blocks
==16474== still reachable: 449,722 bytes in 9,700 blocks
==16474== suppressed: 0 bytes in 0 blocks
==16474== Rerun with --leak-check=full to see details of leaked memory
==16474==
==16474== For counts of detected and suppressed errors, rerun with: -v
==16474== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.