Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 12 Mar 2004 09:21:16 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Problems running Jabberd v1.4.3 under cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork() Message-ID: <20040312142116.GB17661@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <6.0.1.1.0.20040311192701.03a45640@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Reply-To: cygwin@cygwin.com Note-from-DJ: This may be spam On Fri, Mar 12, 2004 at 01:28:02AM -0500, Frank Seesink wrote: >Basically, no, I haven't been able to reproduce it outside of Jabberd. > >Then again, I don't have a lot of custom source to compile/use. My >simple test program (the one which loaded a DLL which in turn did a >fork()) worked fine, but that was an uber-simple app. > >Jabberd fires up multiple threads/processes with more than one >fork()/spawn_() call prior to reaching the dnsrv module where the final >fork() breaks the camel's back as it were. For the record, this problem usually indicates the need to run 'rebaseall'. -- 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/