ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 7391] Wireshark crashes on bootp filter

Date: Fri, 22 Jun 2012 05:50:18 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7391

--- Comment #8 from Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx> 2012-06-22 05:50:17 PDT ---
(In reply to comment #5)
> Thanks for the detailed explanation :)
> As a workaround, and so as to restore a behavior similar to 1.6.X branch

If you want workaround for crash it's enough if you type '04 ==
bootp.option.value' ;-)

(This workaround sucks, cause it might give you lot of false positives. 
It'll use boolean comparision also for integer values)

> maybe be could consider renaming the new bootp.option.value filters 
> with something like bootp.option.value.8bits and co ?

Generally I really like idea to have same name for similar fields.
And we need general fix not only for bootp, IMHO option 5 from bug #2402
comment 1 would be best one.

We could also add new operators like '===' (blah, php ;/) when value and type
is the same.


But, if you want to rename fields please note that you don't need seperate
entries when comparision functions are the same (like for int8, int16, int32.
Not sure about uint*).

And users will hate us when he or she need to type: bootp.option.value_int8 ==
04 || bootp.option.value_int16 == 04 || bootp.option.value_int32 == 04 ||
bootp.option.value_uint8 == 04 ... :)

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.