Corinna,
On Mon, Jan 13, 2003 at 11:59:20PM +0100, Corinna Vinschen wrote:
I guess it's actually a fault in Cygwin's mmap() implementation but I
don't see the cause so far. I'd greatly appreciate if you could put
some effort into analyzing the problem.
Sure. I'll do whatever I can to help.
On Tue, Jan 14, 2003 at 09:58:03AM -0500, Jason Tishler wrote:
Instead of the above, I have attached for a small testcase, mmap-test.c,
that reproduces the problem. When mmap-test is run, you should get
something like the following output:
Jason,
thanks, that's better than anything else!
Corinna,
On Tue, Jan 14, 2003 at 04:13:21PM +0100, Corinna Vinschen wrote:
On Tue, Jan 14, 2003 at 09:58:03AM -0500, Jason Tishler wrote:
Instead of the above, I have attached for a small testcase,
mmap-test.c, that reproduces the problem. When mmap-test is run,
you should get something
On Tue, Jan 14, 2003 at 10:53:46AM -0500, Jason Tishler wrote:
And in this case it's definitely a Cygwin problem which I should have
a fix for pretty soon.
Cool!
Hi Jason,
I've just commited a fix to the cvs repository. Could you please test
it with vsftpd? Your test application runs
On Tue, Jan 14, 2003 at 09:42:57PM +0100, Corinna Vinschen wrote:
On Tue, Jan 14, 2003 at 10:53:46AM -0500, Jason Tishler wrote:
And in this case it's definitely a Cygwin problem which I should have
a fix for pretty soon.
Cool!
I've just commited a fix to the cvs repository. Could you
On Tue, Jan 14, 2003 at 03:53:43PM -0500, Christopher Faylor wrote:
On Tue, Jan 14, 2003 at 09:42:57PM +0100, Corinna Vinschen wrote:
On Tue, Jan 14, 2003 at 10:53:46AM -0500, Jason Tishler wrote:
And in this case it's definitely a Cygwin problem which I should have
a fix for pretty soon.
On Tue, Jan 14, 2003 at 09:57:15PM +0100, Corinna Vinschen wrote:
On Tue, Jan 14, 2003 at 03:53:43PM -0500, Christopher Faylor wrote:
I'm generating a snapshot right now. If this seems to work ok, I'll
release 1.3.19.
Oooh, wait! I just found out that I missed a bit...
Ok, it should be
Corinna,
On Tue, Jan 14, 2003 at 09:57:15PM +0100, Corinna Vinschen wrote:
On Tue, Jan 14, 2003 at 03:53:43PM -0500, Christopher Faylor wrote:
On Tue, Jan 14, 2003 at 09:42:57PM +0100, Corinna Vinschen wrote:
On Tue, Jan 14, 2003 at 10:53:46AM -0500, Jason Tishler wrote:
And in this case
Hi Chris...
Are you just depriving everyone of all of the cool new features in 1.3.19 to
be mean, or is it that Cygwin is really a top secret[click]
From: Corinna Vinschen [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Cygwin vsFTPd porting issues
Date
In my (seemingly) never ending search for a firewall friendly, Cygwin
ftpd server, I finally stumbled across vsFTPd. By firewall friendly,
I mean being able to specifying the range of passive ports used during
data transfers.
Although, vsFTPd does not use autoconf, the code is well factored --
Hi Jason,
On Mon, Jan 13, 2003 at 09:36:24AM -0500, Jason Tishler wrote:
160 37333219 [main] vsftpd 2232 fixup_mmaps_after_fork: ReadProcessMemory failed
for MAP_PRIVATE address 0xB4, Win32 error 299
I will try to dig deeper to determine why ReadProcessMemory() is failing
with
Hi Jason,
On Mon, Jan 13, 2003 at 03:21:11PM -0500, Jason Tishler wrote:
Replacing MAP_PRIVATE with MAP_SHARED worked around the mmap()/fork()
problem. Is this a reasonable accommodation? Or, should I try to get
MAP_PRIVATE to work?
It's not the way to go, unfortunately.
I guess it's
12 matches
Mail list logo