This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Weird problem with gdb 2003-09-20-cvs (cygwin-special)
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: "Demmer, Thomas" <TDemmer at krafteurope dot com>, Cygwin List <cygwin at cygwin dot com>
- Date: Wed, 02 Jun 2004 10:29:43 -0400
- Subject: Re: Weird problem with gdb 2003-09-20-cvs (cygwin-special)
- References: <0706F4CDC397BF4483877BFDA8DBD3A54622A5@kjsdemucshrexc1.eu.pm.com>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
At 04:06 AM 6/2/2004, you 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.
>
>To me this looks like a heap corruption, but where? It used to
>work fine with 1.5.9 and fails now under 1.5.10.
>read_whole_line() is from the snippets collection, which makes me believe
>that the bug is not in this part, but who knows.
>
>Any pointers on where and what to search?
>
I'd recommend starting with the stack traceback. If nothing is obvious
from that and you want to chase your suspicion that something in cygwin1.dll
is causing the problem, you'll need to build the DLL yourself so you can
debug into it.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
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/