Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 13 Jan 2003 15:55:17 +0100 From: Corinna Vinschen To: Cygwin Subject: Re: Cygwin vsFTPd porting issues Message-ID: <20030113145517.GI16529@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: Cygwin References: <20030113143624 DOT GF1012 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030113143624.GF1012@tishler.net> User-Agent: Mutt/1.4i 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 0xB40000, Win32 error 299 > > I will try to dig deeper to determine why ReadProcessMemory() is failing > with ERROR_PARTIAL_COPY (i.e., 299), but any help or pointers will be > greatly appreciated. If you can figure out why that happens, I'd really appreciate a simple testcase. Please compare the above with the strace output generated by mmap(), probably you will find a discrepancy like the address in the above strace output is not inside of a mapped block. It's also a big difference if the mmap is mapped anonymously or to a file since the mmap() code behaves pretty different. Another way would be to remove MAP_PRIVATE from the mmap() call and try again. MAP_PRIVATE is somewhat problematic on Windows hosts, unfortunately. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/