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
Date: Thu, 21 Mar 2002 11:48:51 -0500
From: Christopher Faylor <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: STATUS_ACCESS_VIOLATION, but not on build machine
Message-ID: <20020321164851.GO8437@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <F536EC3453B2D411AD6100508BAF5F9901FAB458 AT bwga521a DOT ts DOT siemens DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F536EC3453B2D411AD6100508BAF5F9901FAB458@bwga521a.ts.siemens.de>
User-Agent: Mutt/1.3.23.1i

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.

cgf
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .

--
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/