Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 1852] packet-g*.c display filter field problems.

Date: Fri, 11 Jan 2008 15:50:52 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1852





------- Comment #4 from christopher.maynard@xxxxxxxxx  2008-01-11 15:50 GMT -------
packet-gsm_a.c: Obviously, this file has not been looked at yet,so it still has
display filter field problems.

packet-gsm_map.c: There still seem to be quite a few with incorrect/no
prefixes.  A few examples:

Line 17642:
    { &hf_Remote_Operations_Information_Objects_local,
      { "local", "Remote-Operations-Information-Objects.local",
Line 21722:
    { &hf_gsm_old_invoke,
      { "invoke", "gsm_old.invoke",
Line 22029:
    { &hf_gsm_ss_ss_Code,
      { "ss-Code", "gsm_ss.ss_Code",

I think the easiest way to find them all is by going to Wireshark's Help ->
Supported Protocols -> Display Filter Fields -> (scroll down to "GSM_MAP - GSM
Mobile Application (gsm_map) [1174 fields]:") -> (continuing scrolling 'til you
find fields not properly prefixed - they usually stand out pretty clearly from
the rest).

Note: I stopped searching for incorrectly prefixed display filter fields after
"packet-g*" due to the boredom of the task.  Maybe someone else can help
continue "packet-h*" - "packet-z*"?  It's very tedious. 


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.