Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Problem with pthead.h - child's thread ending, causes main program to exit
Date:	Fri, 29 Oct 2004 13:28:58 +0100
MIME-Version:	1.0
In-Reply-To:	<Pine.GSO.4.61.0410281221200.11727@slinky.cs.nyu.edu>
Message-ID:	<NUTMEGbZvFqV2mEIkLe00000338@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	29 Oct 2004 12:28:58.0718 (UTC) FILETIME=[DD42AFE0:01C4BDB2]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Igor Pechtchanski
> Sent: 28 October 2004 17:24

> On Thu, 28 Oct 2004, jdeifik wrote:
> 
> > > On Wed, 27 Oct 2004, jdeifik wrote:
> > >
> > > > When I run the program with gdb, I get really weird segmentation
> > > > faults, for example:
> > >
> > > http://www.cygwin.com/ml/cygwin/2004-10/msg01033.html
> 
> Does anyone know gdb macros well enough to say off-hand whether it's
> possible to write a function to ignore those particular SEGVs?

  I dunno the language syntax, but I can see the design: set a breakpoint on
IsBadWritePtr, and have a macro routine that is called by that breakpoint,
that 1) issues the 'handle' instruction 2) issues a 'finish' to step until
out of IsBadWritePtr 3) cancels the 'handle' instruction 4) issues a 'cont'
to let the app continue running.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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