From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25793 invoked by alias); 31 Oct 2003 02:26:23 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 25657 invoked from network); 31 Oct 2003 02:26:23 -0000 Received: from unknown (HELO redhat.com) (24.131.133.249) by sources.redhat.com with SMTP; 31 Oct 2003 02:26:23 -0000 Received: by redhat.com (Postfix, from userid 201) id 97F5F32A8A7; Thu, 30 Oct 2003 21:26:19 -0500 (EST) Date: Fri, 31 Oct 2003 04:23:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: forking from a DLL? Message-ID: <20031031022619.GA22403@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3FA1BFF5.2000905@easyconnect.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA1BFF5.2000905@easyconnect.fr> User-Agent: Mutt/1.4.1i X-SW-Source: 2003-10/txt/msg01810.txt.bz2 On Fri, Oct 31, 2003 at 02:50:45AM +0100, Pierre-Philippe Coupard wrote: >Does anybody know what my problem might be? is it possible to fork in a >DLL at all, in fact? forking in a DLL should be possible but given the strange way that windows loads dlls into different addresses in child processes, it is probably not going to work in practice. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam@sourceware.org and be permanently blocked from mailing lists at sources.redhat.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/