[Winpcap-users] WinPcap 3.1/WinPcap 3.1 beta

[Guy Harris]

Steev H. wrote:

> 	This is because the beta accepted NULL for the error buffer
> (errbuf), whereas the release version des not :)

Passing a null pointer for the errbuf argument to any of the 
libpcap/WinPcap routines that have such an argument is an error - 
they'll all attempt to fill in the buffer if an error occurs.

(Any application that doesn't check for an error in any libpcap/WinPcap 
call that can return an error is arguably broken, and any application 
that doesn't include errbuf in the error message it reports, or 
otherwise make it available, is also arguably broken, as that 
information might be required to fully diagnose the problem.)