On Mon, Jan 27, 2003 at 10:14:33PM +0100, Martin Regner wrote: > It would be interesting to know more about what protocol dissector > that seems to cause this problem,
I looked for all calls to "proto_tree_add_int()", and didn't find any that were putting into the protocol tree anything other than an FT_INT8, FT_INT16, FT_INT24, or FT_INT32; if there is one, it's going to take more work to find, so, yes, knowing what protocol has the problem would make it a lot easier to fix the problem.
