Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 2 Jun 2004 11:04:15 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Weird problem with gdb 2003-09-20-cvs (cygwin-special) Message-ID: <20040602150415.GD5787@coe.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <0706F4CDC397BF4483877BFDA8DBD3A54622A5 AT kjsdemucshrexc1 DOT eu DOT pm DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0706F4CDC397BF4483877BFDA8DBD3A54622A5@kjsdemucshrexc1.eu.pm.com> User-Agent: Mutt/1.4.1i On Wed, Jun 02, 2004 at 10:06:06AM +0200, Demmer, Thomas wrote: >Hi list, >I have encountered a strange situation that I can boil down to >the attached test case. To reproduce the problem >issue >$ echo 123 > a.dat >$ gcc -Wall -pedantic -o insi insi.c > >The program runs fine when run from the command-line. Running >within insight or gdb the sscanf dies with >(gdb) run >Starting program: /m/c/insi.exe > >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 -- 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/