Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Tue, 13 Nov 2001 19:23:48 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: GDB error
Message-ID:	<20011114002348.GB790@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5 DOT 0 DOT 0 DOT 25 DOT 0 DOT 20011113160248 DOT 021567c0 AT mail DOT nucleus DOT com>
Mime-Version:	1.0
In-Reply-To:	<5.0.0.25.0.20011113160248.021567c0@mail.nucleus.com>
User-Agent:	Mutt/1.3.23.1i

On Tue, Nov 13, 2001 at 04:25:42PM -0700, Simpson Gilbert wrote:
>I searched the archives on Friday for references to the problem I'm having 
>and found several but didn't see a solution. If anyone can point me in the 
>right direction I would be grateful.
>
>I have a small c++ program that compiles and runs, under g++, with no 
>problem. When I try to use GDB I get an error the moment I run the file.
>
>g++ -o linked.exe -g linked.cxx
>gdb -se linked.exe
>
>I get a popup window that says:
>
>Program received signal SIGSEGV, Segmentation fault
>
>and I cannot go any further. No window ever actually pops up that I can 
>issue GDB commands in.
>
>The error also occurs when I add the -nw flag to gdb but I get different 
>info:
>
>gnu GDB 5.0 (20010428-3)
>....
>run
>(I get 4 files listed all with the "error reading line numbers" message)
>/cygdrive/c/WINNT/System32/KERNEL32.dll
>/cygdrive/c/WINNT/System32/advapi32.dll
>/cygdrive/c/WINNT/System32/psapi.dll
>/cygdrive/c/WINNT/System32/IMAGEHLP.dll
>
>Program received SIGSEGV, segmentation fault
>0x77f6ce0c in ?? ()
>
>---
>
>I'm really new to Unix and even newer to CYGWIN so I'm completely lost as 
>to what to do next. I ran setup on Friday and it updated GCC and CYGWIN, I 
>ran it again today and it updated CYGWIN again so I'm pretty sure that I'm 
>current on everything.

This would be one of those "there is something wrong with gdb" errors.

This would also be one of those errors where if I can't duplicate it, I
can't fix it.

Usually, when people have errors with gdb there is a flurry of
discussion where people compare hat sizes, favorite colors, mother's
maiden names, etc.  in an enthusiastic attempt to get to the root of the
problem.

What is always lacking, however, is any actual attempt to debug gdb
itself.

What that means is that the problem will go unfixed for the foreseeable
future.  Sorry.  It isn't good news but it is the most accurate news
there is, currently.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -