| Bug ID |
11700
|
| Summary |
Buildbot crash output: fuzz-2015-11-10-31919.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2015-11-10-31919.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-2015-11-10-31919.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/c06-ldapv3-app-r1.pcap.gz
Build host information:
Linux wsbb04 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=3355
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=0b3091fa359492a0fe7af50a42a2f70d85377a35
Return value: 0
Dissector bug: 0
Valgrind error count: 1
Git commit
commit 0b3091fa359492a0fe7af50a42a2f70d85377a35
Author: Gloria Pozuelo <[email protected]>
Date: Tue Nov 3 16:49:32 2015 +0100
GTP sequence number fix for allowing to have sequence number equal to 0
Change-Id: Id8aad52198905eb33ecccf5ace01287954f31d2e
Reviewed-on: https://code.wireshark.org/review/11526
Petri-Dish: Pascal Quantin <[email protected]>
Reviewed-by: Pascal Quantin <[email protected]>
Command and args: ./tools/valgrind-wireshark.sh
==1861== Memcheck, a memory error detector
==1861== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==1861== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==1861== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2015-11-10-31919.pcap
==1861==
==1861==
==1861== HEAP SUMMARY:
==1861== in use at exit: 1,128,410 bytes in 32,527 blocks
==1861== total heap usage: 2,830,542 allocs, 2,798,015 frees, 159,454,192
bytes allocated
==1861==
==1861== LEAK SUMMARY:
==1861== definitely lost: 44,812 bytes in 2,744 blocks
==1861== indirectly lost: 63,408 bytes in 1,733 blocks
==1861== possibly lost: 0 bytes in 0 blocks
==1861== still reachable: 1,020,190 bytes in 28,050 blocks
==1861== suppressed: 0 bytes in 0 blocks
==1861== Rerun with --leak-check=full to see details of leaked memory
==1861==
==1861== For counts of detected and suppressed errors, rerun with: -v
==1861== 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.