http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2190
------- Comment #1 from jyoung@xxxxxxx 2008-01-13 08:21 GMT -------
Created an attachment (id=1377)
--> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=1377&action=view)
Examples of the inconsistent voip graph analysis reports
This is a text file showing the difference between a "good" VoIP graph analysis
report and the "bad" graph analysis reports that are generated if
RTP_packet_draw() is called multiple times during the TAP.
All of the "bad" Graph Analysis reports were triggered by executing Wireshark
in gdb. Once gdb was started a breakpoint was created for the "retap_packet"
function.
gdb was started on linux with the following command, a breakpoint was added for
the "retap_packet" function and then Wireshark was asked to run:
> # libtool --mode=execute gdb --args ./wireshark
> GNU gdb 6.3
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
<snip>
> (gdb) b retap_packet
> Breakpoint 1 at 0x806ed47: file file.c, line 1849.
> (gdb) run
> Starting program: /home/jyoung/projects/wireshark/.libs/lt-wireshark
> [Thread debugging using libthread_db enabled]
> [New Thread 1111321248 (LWP 14156)]
<snip>
Once Wireshark was started, the file "voip.call2.pcap" was opened.
Once the trace file was opened the Stastics -> "Voip Calls" menu item was
selected.
Selecting the "VoIP Calls" menu item triggered the "retap_packet" breakpoint.
In gdb a "continue XXXX" command was entered where XXXX represents the next
number of breakpoints crossings that gdb should ignoe. I typically choose
values like 500 or 1000.
After entering a value like "c 500" into gdb, gdb will continuing processing
until the "retap_packet" breakpoint has been crossed 499 more times.
When the gdb next halts because of the breakpoint simply hit the <ENTER> for
gdb to automatically issue the last command ("c 500")
Continue pressing <ENTER> until the VoIP Calls window is completly displayed.
Once the "VoIP Calls" window is completely displayed click on the "Select All"
button to select the call.
Once the call has been selected click on the "Graph" button to open the Graph
Analysis window.
If using the voip.call2.pcap file, the "bad" graph analysis report will
generally vary depending on the number of breakpoints that are ignored.
The trace file "voip.call2.pcap" will be uploaded shortly.
--
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.
