Nitesh Gupta wrote:
I guess I have confirmed that there IS an error in parsing the Filter String.
No, there's an error in optimizing the code generated for the filter string. I've checked a fix into the libpcap source tree; the WinPcap people *might* want to pick up that fix for WinPcap 3.1 (I don't think there's a plan to release a libpcap 0.8.4; a libpcap 0.9 might come out in the not-too-distant future, but I don't know whether the WinPcap developers want to switch from 0.8.x to 0.9.x this late in the WinPcap 3.1 release cycle). The fix is the change to optimize.c that fixes it not to eliminate a basic block if it loads into the index register a value that it didn't already have.
================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[email protected]/
To unsubscribe use mailto: [EMAIL PROTECTED]
==================================================================
