Hi.
There was a bug in pcap_dump_open. We have fixed it in our source tree, and
it will be present in the next release of WinPcap.
Have a nice day
GV
----- Original Message -----
From: "Tan Victor-A18027" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 10, 2004 3:35 AM
Subject: [WinPcap-users] Error in pcap_dump_open
> When pcap_dump_open(devhandle, filename) is called for a filename which is
read-only, I see the following using Purify:
>
> [E] NPW: NULL pointer write in EnterCriticalSection {1 occurrence}
> Writing 24 bytes to 0x00000020 (24 bytes at 0x00000020 illegal)
> Address 0x00000020 points into invalid memory
> Thread ID: 0x84c
> Error location
> [KERNEL32.dll ip=0x6c5733c8]
> [wpcap.dll ip=0x10015442]
> [wpcap.dll ip=0x1001583a]
>
CInterface::writeCaptureFileHeader(basic_string<char,char_traits<char>::std,
allocator<char>::std>::std const&) [interface.cpp:746]
> // write file header
> pcap_dumper_t *dump = 0;
> try {
> => pcap_dump_open(mDeviceHandle, fileName.c_str());
>
> }catch(...) {
> // close the device if we have opened it
>
>
> Subsequent calls to pcap_dump_open sometimes produced unexpected results.
>
> Can somebody explain whether this is this a known bug?
>
>
> Thanks,
> Victor
>
>
> ==================================================================
> This is the WinPcap users list. It is archived at
> http://www.mail-archive.com/[EMAIL PROTECTED]/
>
> To unsubscribe use
> mailto: [EMAIL PROTECTED]
> ==================================================================
>
==================================================================
This is the WinPcap users list. It is archived at
http://www.mail-archive.com/[EMAIL PROTECTED]/
To unsubscribe use
mailto: [EMAIL PROTECTED]
==================================================================
