[Winpcap-users] WinPcap 3.1 beta 4 memory leak? crashes?

Guy Harris guy at alum.mit.edu
Sat May 21 20:41:45 GMT 2005


Tom Brown wrote:
> Are there any issues with calling 
> pcap_findalldevs() every half second?

As long as you call "pcap_freealldevs()" on the results of the 
"pcap_findalldevs()" when you're finished with the results, so that you 
don't leak the data structures allocated by "pcap_findalldevs()", the 
only issues should be the CPU time it takes (and that it might attempt 
to open all the devices it finds for capturing, to make sure they can be 
used for capturing; all versions in libpcap on UN*X do that, but some 
versions in WinPcap might not).

On the other hand, I'm not sure why, if you're looking for Ethernet 
devices, I'm not sure why they'd show up later if they didn't show up 
right away - I suspect that the Ethernet device should show up in a 
pcap_findalldevs() call regardless of whether it's plugged in or not, 
but perhaps it somehow doesn't show up if it's not plugged in.

What sort of status are you getting from the device?



More information about the Winpcap-users mailing list