On Tue, May 13, 2014 at 8:19 PM, Kevin Cox <kevincox@xxxxxxxxxxx> wrote:
> Hello,
>
Hi Jevin,
> I was attempting to dissect a 64 bit bitfield and was wondering what the
> best/preferred method was. I saw a question on ask.wireshark.org[0]
> which had a single answer the said to use a text field.
>
> [0]
> http://ask.wireshark.org/questions/20599/dissecting-bitfields-larger-than-32-bits
>
The better will be add 64bits bitfields... ;-)
> I was wondering if there is a better way to do this. My best idea would
> be to parse it as two separate 32 bit bitfields however this is not as
> elegant. If I was to parse it this way I also don't know what values to
> set in the hf struct either.
>
> { &hf_a_field, {
> "Name", "id",
> FT_BOOLEAN, 32, NULL, MY_MASK,
> NULL, HFILL
> } },
>
> What should the parent bitfield length be? I think it should be 32 but
> I'm not sure.
No problem to use 2 separate bitfields
for the parent, you have the choice
>
> Thanks in advance for any recommendations.
>
> Kevin
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe