Problems running Jabberd v1.4.3 under Cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()

2004-03-11 Thread Frank Seesink
QUESTION: Is there an issue in Cygwin 1.5.7 (and still in the 20040306 snapshot) that might cause a program which has been working back in November 2003 to suddenly stop doing so, specifically in its communication with a secondary executable which it forks/launches to do DNS resolution? Second

Re: Problems running Jabberd v1.4.3 under Cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()

2004-03-11 Thread Larry Hall
At 07:03 PM 3/11/2004, you wrote: >At this point, I do not know if I am chasing my tail or not. When an application >suffers this Win32 error 487 message, is it usually an indication of some glitch in >cygwin1.dll, or is it as the message seems to indicate, either some sort of issue of >not eno

Re: Problems running Jabberd v1.4.3 under Cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()

2004-03-11 Thread Frank Seesink
Hey Larry, 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 multi

Re: Problems running Jabberd v1.4.3 under cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()

2004-03-12 Thread Christopher Faylor
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,

Re: Problems running Jabberd v1.4.3 under cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()

2004-03-13 Thread Frank Seesink
Hey Chris, For the record, I tried this. No dice. Tried rebaseall with Cygwin 1.5.7, then with the latest snapshot at the time (20040306), and as I mentioned in my original post, I even used a modified version of rebaseall to rebase the DLLs generated by Jabberd (which are run from their bui

Re: Problems running Jabberd v1.4.3 under cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()

2004-03-13 Thread Christopher Faylor
On Sat, Mar 13, 2004 at 05:26:40PM -0500, Frank Seesink wrote: >I see your name on the list quite a bit, and you seem to be one of the >key guys "in the know." Can you possibly explain to me what the error >usually indicates? I mean, beyond the rebaseall, what exactly are we >talking about? A