I tried continuing, it hangs for about 5 minutes, then displays "Can't read instruction at " and some address starting with 7.
-Rolf > -----Original Message----- > From: Christopher Faylor [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 7:41 PM > To: [EMAIL PROTECTED] > Subject: Re: GDB always receives sigsegv with cygwin 1.3.13-2 > > > On Tue, Oct 15, 2002 at 07:37:31PM -0400, Rolf Campbell wrote: > >I tried it with 2 different executables (both C++, both > compiled with > >GCC3.2). I tried it with both the stock gdb (20010428-3) & the one > >listed as experimental (20020718-1). I also tried it with both > >1.3.13-2 & 1.3.12-4. > > > >The test was, set a breakpoint at the first line of main (done by > >default by the gui), and click the run button. With both programs & > >both versions of GDB, the results were the same: With 1.3.12-4, it > >worked fine. With 1.3.13-2, gdb got the sigsegv signal. > > You can ask Robert Collins about this. This is in pthreads > code. There is some pointer validation going on that causes > this. There are two of these, in fact. I meant to mention > them in cygwin-developers but I forgot. > > Just continue beyond the SIGSEGV and you should be ok. > > 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/ > > -- 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/
