Yes, it is. I also use this structure to display information in the COL_INFO and in the proto_tree_add_protocol_format() using the rval_to_str(), and it works.
I tried to just add the item in the tree but it is impossible if I don't have also the hf declared in the hf_register_info, so maybe it is in the proto_tree_add_uint() call.
I don't use SVN, so my old (beginning of March, 1.0.6 -27387) version might have a bug, but I haven't seen anything about this in the previous messages. Was the update of proto.c a good idea?
As I can't send the complete code (internal use), is there a dissector that uses the range_string structure as I need?
Thanks a lot for your help, Chris
Yvan
De : "Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>
À : Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Envoyé le : Mardi, 14 Avril 2009, 17h47mn 14s
Objet : Re: [Wireshark-dev] RVALS in display filters
Everything looks OK to me. How is afdx_type
declared? Does it match the README.developer’s example?
static const range_string rvalstringname[] = {
{ INTVAL_MIN1, INTVALMAX1, "Descriptive String
1" },
{ INTVAL_MIN2, INTVALMAX2, "Descriptive String
2" },
{ 0, 0, NULL }
};
- Chris
From:
wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of yvanmmailbox-web@xxxxxxxx
Sent: Tuesday, April 14, 2009 9:32 AM
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] RVALS in display filters
Hi
all,
I am working on a dissector plugin.
I have a problem with the use of RVALS in display filter. As indicated in
README.developer, I wrote my code like that:
...
guint8 type = 0;
....
type = tvb_get_guint8(tvb, 29);
...
proto_tree_add_uint(afdx_tree, hf_type, tvb, 29, 1, type);
...
{ &hf_type,
{ "Data
type ", "afdx.type", FT_UINT8, BASE_DEC|BASE_RANGE_STRING,
RVALS(afdx_type), 0x0,
"Type of data carried", HFILL }},
I changed my file proto.c as indicated in this url, because it didn't integrate
the BASE_RANGE_STRING:
http://www.nabble.com/rev-26257:--trunk-epan---trunk-epan-:-proto.c-td19639466.html
But it does not solve the problem. I still can't run WireShark with this code
in my plugin, and the problem seems to come from RVALS or interpretation of
BASE_RANGE_STRING.
Does anyone can help me?
Thanks a lot!
Yvan
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.