Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.0.1.1.0.20040311192701.03a45640@127.0.0.1>
X-Sender: 
Date: Thu, 11 Mar 2004 19:32:41 -0500
To: Frank Seesink <frank AT mail DOT wvnet DOT edu>, cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Problems running Jabberd v1.4.3 under Cygwin v1.5.7  (or latest snapshot), and heap allocation error caused by fork()
In-Reply-To: <c2quo3$qsq$1@sea.gmane.org>
References: <c2quo3$qsq$1 AT sea DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

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/