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
Content-Type: text/plain;
  charset="iso-2022-jp"
From: Max Zaitsev <maksik AT gmx DOT co DOT uk>
Reply-To: maksik AT gmx DOT co DOT uk
Organization: Mutella Dev co.
To: aloha <aloha AT bradea DOT com>, cygwin AT cygwin DOT com
Subject: Re: pthread problem
Date: Wed, 3 Jul 2002 12:59:43 +0200
User-Agent: KMail/1.4.1
References: <3D22D421 DOT 2050102 AT bradea DOT com>
In-Reply-To: <3D22D421.2050102@bradea.com>
MIME-Version: 1.0
Message-Id: <200207031259.43097.maksik@gmx.co.uk>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g63B1Qn07633

I'm suffering from the similar problem. Just posted a question here today. 
When I used older version of cygwin, GDB used to crash somewhere in the 
static objects initialization, with 1.3.11 it goes a bit further, but not 
far. and without debugger my program runs just until first wait conditions 
are used.

--Max

On Wednesday 03 July 2002 12:38, aloha wrote:
>  I have a multi-threaded application written in C++ that works fins in
>  linux, solaris and windows, but crashes in cygwin, and I even cannot
>  debug it with gdb in cygwin, when I run it, I just got a sigsegv, and
>  the stack seems to be corrupted, usually in a function
>  "_libkernel32_a_iname", and the source window outputs "Unable to Read
>  Instructions at 0x6106c7d0"
>  Can anyone help me ?
>  thanks
>  rgds
>  aloha



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