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
Message-ID: <0706F4CDC397BF4483877BFDA8DBD3A54622AF@kjsdemucshrexc1.eu.pm.com>
From: "Demmer, Thomas" <TDemmer AT krafteurope DOT com>
To: Cygwin List <cygwin AT cygwin DOT com>
Cc: "'wirawan AT camelot DOT physics DOT wm DOT edu'" <wirawan AT camelot DOT physics DOT wm DOT edu>
Subject: Re: Weird problem with gdb 2003-09-20-cvs (cygwin-special)
Date: Thu, 3 Jun 2004 10:58:57 +0200
MIME-Version: 1.0
Content-Type: text/plain

cgf wrote:
>On Wed, Jun 02, 2004 at 10:06:06AM +0200, Demmer, Thomas wrote:
>>Hi list,
[...]
>>
>>Program received signal SIGSEGV, Segmentation fault.
>>0x77e75a3f in KERNEL32!IsBadWritePtr () from
>>/c/WINDOWS/system32/kernel32.dll
>>
>>This does not happen when compiled with -mno-cygwin.
>
>Just continue through this error.  IsBadWritePtr throws a SEGV
>exception.  This is normal.
>
>cgf

Setting a breakpoint after the sscanf() and continuing a couple of times
eventually 
helped, thanks you (contrary to what was reported in 
http://sources.redhat.com/ml/cygwin/2004-06/msg00075.html ).

Is this "normal" behavior expected to go away again? :-)


Ciao
Tom


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