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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: GDB always receives sigsegv with cygwin 1.3.13-2 Date: Wed, 16 Oct 2002 13:21:14 -0400 Message-ID: <83040F98B407E6428FEC18AC720F5D732DB72F@exchange.tropicnetworks.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rolf Campbell" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9GHLO825761 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. -Rolf > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Wednesday, October 16, 2002 12:26 PM > To: cygwin AT cygwin DOT com > Subject: Re: GDB always receives sigsegv with cygwin 1.3.13-2 > > > On Wed, Oct 16, 2002 at 12:14:24PM -0400, Rolf Campbell wrote: > >It stops at "_libkernel32_a_iname" with "Unable to Read > Instruction at > >0x77e88207". > > That's not really useful. What's the backtrace? > > -- > 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/ > > -- 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/