https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5666
Summary: The Sniffer/NetXRay code in the wiretap module is not
incrementing wtap_dumper.bytes_dumped
Product: Wireshark
Version: 1.4.3
Platform: All
OS/Version: All
Status: NEW
Severity: Minor
Priority: Low
Component: Extras
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: robert@xxxxxxxxxxxxxx
Created an attachment (id=5919)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5919)
Proposed patch of netxray.c.
Build Information:
Version 1.4.3 (SVN Rev 35482 from /trunk-1.4)
Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 (32-bit) with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jan
11 2011), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
I have not observed any bugs as a result of this yet. But if anything depends
on wtap_dumpter.bytes_dumped field being correctly incremented, then there will
be a problem. And although the field itself is "internal", its value can be
retrieved via the wtap_get_bytes_dumped() API, making it a publicly accessible
bug.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.