Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 16 Oct 2002 15:52:35 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: GDB always receives sigsegv with cygwin 1.3.13-2 Message-ID: <20021016195235.GA21826@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <83040F98B407E6428FEC18AC720F5D732DB72F@exchange.tropicnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83040F98B407E6428FEC18AC720F5D732DB72F@exchange.tropicnetworks.com> User-Agent: Mutt/1.4i On Wed, Oct 16, 2002 at 01:21:14PM -0400, Rolf Campbell wrote: >GDB does not 'crash', so it does not produce a traceback. The only >traceback that I can get is of the program I'm debugging, which I don't >think is meaningful, and I can't seem to copy/paste from the gdb console >window. Huh? You said that you're getting a sigsegv. A backtrace from that would probably be informative. You copy and paste from the gdb console window just like you do on any command line window. Click on the icon in the upper left corner of the window, and there will be options for "mark", "copy" (or is it "cut") and paste. If that isn't clear then use rxvt. 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/