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
X-Authentication-Warning:	thing1-200.fsi.com: ford owned process doing -bs
Date:	Thu, 15 Apr 2004 21:55:16 -0500 (CDT)
From:	Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender:	ford AT thing1-200
Reply-To:	cygwin AT cygwin DOT com
To:	Jeremy Song <jeremy AT ubist DOT co DOT kr>
cc:	cygwin AT cygwin DOT com
Subject:	Re: KERNEL32!IsBadWritePtr () error raised while debugging thread test program.
In-Reply-To:	<003301c4235d$99229e50$4f2e6ade@jsong>
Message-ID:	<Pine.GSO.4.58.0404152152060.19315@thing1-200>
References:	<003301c4235d$99229e50$4f2e6ade AT jsong>
MIME-Version:	1.0
X-IsSubscribed:	yes

Please try to configure your mailer to wrap lines at <= 80 chars.  Thanks.

On Fri, 16 Apr 2004, Jeremy Song wrote:

> I made a simple multi-threaded application with g++ for cygwin and it
> runs well but if I try to debug my program, it shows just SIGSEGV
> Segmentation fault like the following. I can't even get into the main
> though...If I move out the lines for creating threads, it works fine.

This is a known "issue", PTC.  The work-around is to just continue.  I
know, I know.  Who ever head of a SIGSEGV you could continue from?  Just
trust me, it works ;-).

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

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

- Raw text -