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: <F536EC3453B2D411AD6100508BAF5F9901FAB459@bwga521a.ts.siemens.de>
From: Kandziora Jan <Jan DOT Kandziora AT ts DOT siemens DOT de>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: AW: STATUS_ACCESS_VIOLATION, but not on build machine
Date: Tue, 26 Mar 2002 10:02:28 +0100
MIME-Version: 1.0
Content-Type: text/plain

Christopher wrote
>
>>I've got the same problem with a self-engineered program here.  For
-----Snip-----
>>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.
>
Nice, Christopher. I've done this for at least 3 month, ever and ever again.
I suspect three possible problems:
1. I do not fully understand how (v)printf works. Maybe.
2. I'm to blind, frustated etc. to understand gdb's output. Most likely now.
3. I depend on something not portable. Happens often.

What I do not understand is why the problem only occur if Cygwin is using
DOS linefeeds. The same program works fine with UNIX linefeeds. What's
the difference from the application's point of view?

>
> 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.
>
Sorry, I have to find my protecting coat of sarcasm, so I shut up now.

	Jan


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