Greetings, I am experiencing an incredibly nasty bug in my application using the latest WinPCap 3.1B3. I assume the bug is in my code, so am reducing it down to a minimal-code case to prove/disprove that.
Here's my question: If there were a deadlock bug in NPF.SYS (like the proverbial "JMP -1" or "jump self", if you prefer) infinite loop, could that cause: 1) Application becomes totally unresponsive, showing zero CPU consumption 2) The debugger cannot halt the application 3) Windows cannot halt the application, and Windows can't shut down 4) On rare occasions, an instantaneous Windows crash+reboot, without even a blue screen That's what I've been hammering on all day. Blessedly, the bug is 100% repeatable, so I should get down to a minimum code example (or figure out what I'm doing wrong) pretty quickly. In any case, having never developed an NDIS Minport driver (or any other Windows driver), I'm curious whether this type of symptom set would be familiar to someone who has developed one. I've never seen anything like this before. Thanks to all, Rob--- ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
