This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problems running Jabberd v1.4.3 under Cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: Frank Seesink <frank at mail dot wvnet dot edu>, cygwin at cygwin dot com
- Date: Thu, 11 Mar 2004 19:32:41 -0500
- Subject: Re: Problems running Jabberd v1.4.3 under Cygwin v1.5.7 (or latest snapshot), and heap allocation error caused by fork()
- References: <c2quo3$qsq$1@sea.gmane.org>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
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 enough stack/heap space, or worse, some kind of access violation where the program is attempting to access memory it should not?
Here's what Windows says about error # 487:
# net helpmsg 487
Attempt to access invalid address.
So it would appear that your last guess is the proper one. Can you
reproduce it outside of Jabberd?
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
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/