Wireshark-dev: Re: [Wireshark-dev] range_string problem
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Stephen Fisher <stephentfisher@xxxxxxxxx>
Date: Mon, 5 Feb 2007 12:56:26 -0800
On Thu, Jan 25, 2007 at 10:06:00AM +0530, jaiswal.vikash@xxxxxxxxx wrote:

> I've tried to use range_string in my dissector in the following way , 
> but it's giving an error .
>  
> { &hf_xyz_vlr_cfdata_ncrt,
>    {    "No reply condition time",  "xyz.vlr_cfdata_ncrt",    FT_UINT8,
> BASE_DEC,       RVALS(vlr_cfdata_nrct_rvals),   0x0,    "",     HFILL
> }},

> I've tried with RVALS(vlr_cfdata_nrct_rvals) and 
> RS(vlr_cfdata_nrct_rvals) , but both gave the error . Is there any 
> header we need to include for using range_string .

We haven't implemented RVALS() / RS() in Wireshark yet, but are working 
on it right now. For the time being, you can use match_strrval() and 
rval_to_str() as described in doc/README.developer.


Steve