[Paul Offord <Paul.Offord@xxxxxxxxxxxx>]

Hi,

 

I upgraded from 2.2.2 to 2.2.3 a few days ago.  I have a dissector( written in C) that I wrote a while back that works OK with 2.2.2 but not 2.2.3.  With the latter, on Wireshark start up I get:

 

  14:49:57          Err  Field 's-sitename' (iis_log.s_sitename) is a FT_ABSOLUTE_TIME but is being displayed as BASE_NONE instead of as a time

 

My definition for the field registration array is:

 

static hf_register_info hf[] = {

    { &hf_bds_type,

    { "BDS Type", "bds.type",

    FT_UINT16, BASE_DEC,

    vs_type, 0x0,

    NULL, HFILL }

    },

 

    { &hf_bds_format,

    { "BDS Format", "bds.format",

    FT_UINT16, BASE_DEC,

    vs_format, 0x0,

    NULL, HFILL }

    },

 

    { &hf_iis_s_sitename,

    { "s-sitename", "iis_log.s_sitename",

    FT_STRING, BASE_NONE, NULL, 0x0,

    "IIS site name", HFILL } },

 

   .

   .

 

I’m going to do some debugging this evening but I wondered if there have been any changes made to field registration.

 

Thanks and regards…Paul

 

 

______________________________________________________________________

This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.

Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________