| Bug ID |
8459
|
| Summary |
Memory leak in packet-tcp.c
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
All
|
| OS |
All
|
| Status |
CONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.9.1 (SVN Rev 48237 from /trunk)
Copyright 1998-2013 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GLib 2.35.8, with libpcap, with libz 1.2.7, with POSIX
capabilities (Linux), without libnl, with SMI 0.4.8, with c-ares 1.9.1, with
Lua
5.2, without Python, with GnuTLS 2.12.23, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.
Running on Linux 3.8.0-11-generic, with locale en_CA.UTF-8, with libpcap
version
1.3.0, with libz 1.2.7.
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Built using gcc 4.7.2.
--
Revision 48227 exposed a pre-existing memory leak in the TCP dissector.
Issue was first raised here:
https://www.wireshark.org/lists/wireshark-dev/201303/msg00109.html
It's possible to reproduce the issue with valgrind and the capture from bug
#8456.
You are receiving this mail because:
- You are watching all bug changes.