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
Message-Id: <4.3.1.2.20020321120034.02253e38@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 21 Mar 2002 12:01:32 -0500
To: cygwin AT cygwin DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: STATUS_ACCESS_VIOLATION, but not on build machine
In-Reply-To: <20020321164851.GO8437@redhat.com>
References: <F536EC3453B2D411AD6100508BAF5F9901FAB458 AT bwga521a DOT ts DOT siemens DOT de>
 <F536EC3453B2D411AD6100508BAF5F9901FAB458 AT bwga521a DOT ts DOT siemens DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:48 AM 3/21/2002, Christopher Faylor wrote:
>On Thu, Mar 21, 2002 at 09:43:31AM +0100, Kandziora Jan wrote:
> >Mark wrote:
> >>mpeg2enc.exe works fine on the build machine (Win98SE with 64MB), but
> >>bombs out with a STATUS_ACCESS_VIOLATION error on another machine
> >>(Win2K with 256MB).  This machine does not have the Cygwin environment
> >>installed, but I did (of course) copy the DLL across.  I don't believe
> >>there is more than one copy of the DLL on the machine - I'll check
> >>later.
> >>
> >>I know mpeg2enc allocates a lot of memory, and also uses threads.  Any
> >>hints as to what I should check next?
> >>
> >I've got the same problem with a self-engineered program here.  For
> >what I know now, it only happens if no registry keys for Cygwin are
> >present or if I use the "Default Text file Type=DOS" in the setup.  For
> >some reason, I have a "printf"-wrapper in my program.  What do you
> >think the where the execption always occur?  Right: That function.  I
> >use Cygwin 1.3.9 now, but I had the problem with 1.3.2 and 1.3.4 also.
>
>Lets go back to first principals here.  When you see a bug you suspect
>that there is a bug in the program.  To debug a program you use gdb.
>
>It's really simple.  No email to a mailing list required.  No speculation
>that it could be a cygwin version.  You run the program under the debugger
>and find out where the problem is.



But where's the sport in that? ;-) 



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/