Wireshark-bugs: [Wireshark-bugs] [Bug 9116] New: Readme.stats_tree shows the wrong function para

Date: Fri, 06 Sep 2013 17:19:48 +0000
Bug ID 9116
Summary Readme.stats_tree shows the wrong function parameters for stats_tree_register
Classification Unclassified
Product Wireshark
Version 1.9.x (Experimental)
Hardware All
OS All
Status UNCONFIRMED
Severity Major
Priority Low
Component Documentation
Assignee [email protected]
Reporter [email protected]

Build Information:

--
The example and the description just below it in README.stats_tree shows the
wrong parameters for the function call for stats_tree_register.  While the
header has flags as the 4th parameter.

//**********************************
//From README.stats_tree
//From the example
stats_tree_register("udp", /* the proto we are going to "tap" */
                        "udp_terms", /* the abbreviation for this tree (to be
used as -z udp_terms,tree) */
                        st_str_udp_term, /* the name of the menu and window
(use "/" for sub menus)*/
                        udp_term_stats_tree_packet, /* the per packet callback
*/
                        udp_term_stats_tree_init, /* the init callback */
                        NULL ); /* the cleanup callback (in this case there
isn't) */

//From the call description
stats_tree_register( tapname, abbr, name,  packet_cb, init_cb, cleanup_cb);
 registers a new stats tree



//**********************************
//From the header file stats_tree.h
extern void stats_tree_register(const gchar *tapname,
                const gchar *abbr, 
                const gchar *name,
                guint flags,
                stat_tree_packet_cb packet,
                stat_tree_init_cb init,
                stat_tree_cleanup_cb cleanup);

/* registers a new stats tree with default group REGISTER_STAT_GROUP_UNSORTED
from a plugin
 * abbr: protocol abbr
 * name: protocol display name
 * flags: tap listener flags for per-packet callback
 * packet: per packet callback
 * init: tree initialization callback
 * cleanup: cleanup callback
 */


You are receiving this mail because:
  • You are watching all bug changes.