RE: pthreads "problem" Re: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Rolf Campbell
> -Original Message- > From: Christopher Faylor [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 7:54 PM > > Ok. This is occurring in code compiled via gcc 3. gcc 3 > uses a phreads mutex which is assigned to > PTHREAD_MUTEX_INITIALIZER. There is a check for whether the

pthreads "problem" Re: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Christopher Faylor
On Wed, Oct 16, 2002 at 07:07:16PM -0400, Rolf Campbell wrote: >Program received signal SIGSEGV, Segmentation fault. >0x77e88207 in _libkernel32_a_iname () >(gdb) traceback >Undefined command: "traceback". Try "help". >(gdb) backtrace >#0 0x77e88207 in _libkernel32_a_iname () >#1 0x00412820 in

RE: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Rolf Campbell
> -Original Message- > From: Christopher Faylor [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 3:53 PM > > 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

Re: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Christopher Faylor
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

RE: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Rolf Campbell
rom: Christopher Faylor [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 12:26 PM > To: [EMAIL PROTECTED] > 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 "

Re: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Christopher Faylor
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://c

RE: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Rolf Campbell
It stops at "_libkernel32_a_iname" with "Unable to Read Instruction at 0x77e88207". > -Original Message- > From: Rolf Campbell > Sent: Wednesday, October 16, 2002 12:04 PM > To: [EMAIL PROTECTED] > Subject: RE: GDB always receives sigseg

RE: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Rolf Campbell
Both. > -Original Message- > From: Christopher Faylor [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 11:36 AM > To: [EMAIL PROTECTED] > Subject: Re: GDB always receives sigsegv with cygwin 1.3.13-2 > > > On Wed, Oct 16, 2002 at 09:20:18AM -0

Re: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Christopher Faylor
On Wed, Oct 16, 2002 at 09:20:18AM -0400, Rolf Campbell wrote: >I tried continuing, it hangs for about 5 minutes, then displays "Can't >read instruction at " and some address starting with 7. Hmm. Is this with the experimental version of gdb or the crufty version? cgf -- Unsubscribe info:

RE: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-16 Thread Rolf Campbell
[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

Re: GDB always receives sigsegv with cygwin 1.3.13-2

2002-10-15 Thread Christopher Faylor
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 t