https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4964
Summary: The 5th decimal place in tshark avg. SRTst is
sometimes inaccurate; and need for 6 dec places of SRT
precision
Product: Wireshark
Version: 1.5.x (Experimental)
Platform: All
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Low
Component: TShark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: turney_cal@xxxxxxx
CC: turney_cal@xxxxxxx
Cal Turney <turney_cal@xxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #4866| |review_for_checkin?
Flag| |
Created an attachment (id=4866)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4866)
Patch that addresses all of the reported issues
Build Information:
Compiled (32-bit) 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.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5.
Built using Microsoft Visual C++ 9.0 build 30729
--
This is the tshark counterpart of the Wireshark request bug 4956.
1.) The 5th decimal place of the average SRT values in all of the tshark SRT
output tables is sometimes 1us too small due to rounding error. In
tap-dcerpcstat.c, tap-smbstat.c, tap-rpcstat.c and tap-rpcprogs.c the
'tot.nsecs' variable is divided by 10,000, and the result is divided by the
number of calls and stored in 64-bit integer 'td' which causes the remainder to
be truncated. For example, if the total number of nanoseconds (tot.nsecs) is
239,999, and the number of calls (num) is 2, the average SRT using this formula
is 11 (0.00011) (239,999/10,000=23, 23/2=11) but it should be 12 or (.00012).
2.) SRT values are currently displayed in 10 microseconds (10us) but with the
emergence of 10GigE networks, one microsecond (1us) accuracy is increasingly
required for addressing network performance issues.
3.) Unlike the SRT output of DCERPC, ONC-RPC, and ONC-RPC programs in Wireshark
dialogs, tshark outputs a rows for procedures with zero values (no calls). This
should be corrected.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.