http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1591
Summary: dumpcap in ring buffer mode. overflow
Product: Wireshark
Version: 0.99.5
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Low
Component: Extras
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: zheltov@xxxxxxxxx
Build Information:
Version 0.99.5 (SVN Rev 20677)
Copyright 1998-2007 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 with GTK+ 2.10.7, with GLib 2.12.7, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 3.1
(packet.dll version 3, 1, 0, 27), based on libpcap version 0.9[.x], without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
--
I start dumpcap in ring buffer mode without stop conditions. Dumpcap creates
files with the following format: myfile_number_datestamp.cap. the Number
parameter has 5 digits, that means the maximum number of files is 99999. After
approaching the 99999 files, the number changes to 10001 (unexpectedly) and the
most important: if I had ring buffer with MORE THAN ONE file (3 files, 5 files)
before 99999, than after i have only ONE file in ring buffer. This confuses me,
because I expect to see the same amount of files in my ring buffer. Think it
overflow problem in dumpcap code. I tried also on 0.0.3 version of Wireshark
packet - the same problem
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.