http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2190
Summary: Inconsistant VoIP "Graph Analysis" report generated for
same trace file
Product: Wireshark
Version: SVN
Platform: PC
OS/Version: All
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: jyoung@xxxxxxx
Build Information:
Version 0.99.8 (SVN Rev 24073)
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.8.3, with GLib 2.8.1, with libpcap 0.9.2, with libz 1.2.3,
without libpcre, without SMI, without ADNS, without Lua, with GnuTLS 1.2.5,
with
Gcrypt 1.2.1, without Kerberos, with PortAudio PortAudio V19-devel, without
AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.
Running on Linux 2.6.13-15.18-default, with libpcap version 0.9.2.
Built using gcc 4.0.2 20050901 (prerelease) (SUSE Linux).
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Hello,
This is a problem uncovered while working on the now resolved bug 2017...
One symptom of this new bug is that the VoIP "Graph Analysis" report generated
by Wireshark is not always consistent for the same trace file.
The malformed "Graph Analysis" reports are generated if the gtk/voip_calls.c's
RTP_packet_draw() function get called multiple times during a TAP. If the
RTP_packet_draw() function is only called once during the TAP then the
resulting "Graph Analysis" report looks to be correct.
The RTP_packet_draw() appears to be called multiple times if and when the
system that Wireshark is running is very busy. One indication that the system
is "busy" is by the appearance of a temporary "Refiltering statistics on: all
packets" status window.
This problem can be most easily replicated by running Wireshark in valgrind or
by running Wireshark in gdb and inserting some specific breakpoints and/or
watch values.
I will soon upload a text file that illustates the Graph Analysis report
problem along with a trace file that can be used to replicate the 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.
