On Jun 2, 2005, at 3:42 PM, Gianluca Varenni wrote:
Here is a KB documenting it
http://support.microsoft.com/default.aspx?scid=kb;en-us;94248
That's a bit nastier - not only can't a C runtime file handle (the
file descriptors returned by the UNIX-like _open() call and used by
the UNIX-li
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 02, 2005 2:30 PM
Subject: Re: [tcpdump-workers] pcap_dump_file & CO
On Jun 2, 2005, at 11:42 AM, Loris Degioanni wrote:
Trying to understand why the -C tcpdump option doesn't work under
Windows,
On Jun 2, 2005, at 1:35 PM, mcr wrote:
Seems reasonable, but it certainly seems like a Windows.dll silly
to me.
Yes, but, as per my mail, there are arguably other reasons why
pcap_dump_ftell() should exist, namely that applications should have
the idea that a "pcap_dumper_t" is just a
On Jun 2, 2005, at 11:42 AM, Loris Degioanni wrote:
Trying to understand why the -C tcpdump option doesn't work under
Windows, I realized that a file pointer created in a dll can only
be used inside that dll. This is a documented Windows limitation.
So where is this documented?
-
This is t
-BEGIN PGP SIGNED MESSAGE-
The only thing left to do for 3.9 is the Changes file.
At:
http://www.tcpdump.org/changes/2005-05-27.18:25:04.html
is the summary of all commits since 3.8. If someone wanted to go
through that and condense it down to 10-30 lines...
I have these wet dia
-BEGIN PGP SIGNED MESSAGE-
> "Loris" == Loris Degioanni <[EMAIL PROTECTED]> writes:
Loris> - pcap_dump_file and the other functions to make file
Loris> pointers explicit don't have any meaning in Windows, because
Loris> any stdio function will fail with those pointers, so
Loris Degioanni wrote:
Trying to understand why the -C tcpdump option doesn't work under
Windows, I realized that a file pointer created in a dll can only be
used inside that dll. This is a documented Windows limitation.
Gak. That sux. Ethereal's capture file library is also done as a dll
on
Trying to understand why the -C tcpdump option doesn't work under
Windows, I realized that a file pointer created in a dll can only be
used inside that dll. This is a documented Windows limitation.
This means that:
- pcap_dump_file and the other functions to make file pointers explicit
don't h
