Wireshark · Ethereal-dev: [ethereal-dev] [LEEDSNET] Error output & logginf whilst developing ethereal

[Leedsnet <info@xxxxxxxxxxxx>]

> There's plenty of other stuff to be added, too, e.g. information on how
> to make a plugin, and information on the other routines a dissector can
> call.

I am working on a dissector for the Wireless Application Protocol (UDP
ports 920x) based on the README.developer, without which, my attempt
would probably have foundered.

I have discovered that if bad values are sent to
      proto_tree_add_item( )
in a dissector, a segmentation fault is possible (um, likely) in
      _proto_tree_add_item_value( )
in proto.c .

So, are there any known ways of checking for bad values?

Of more relevance to me, is there any harness or infra-structure
for logging or console output, to track values going into procedures?

For all I know this may be built-in to glib, but I have never seen it discussed
here. Currently I an using DDD, and whilst this is an excellent program,
I am not really used to it.

On a separate issue, has putting the packet-*.c sources in their
own directory ever been proposed?

Ben.


--
Leedsnet - The information resource for Leeds and the West Riding
< URL:http://www.leedsnet.com/ >