RE: GDB always receives sigsegv with cygwin 1.3.13-2

RE: GDB always receives sigsegv with cygwin 1.3.13-2

[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: cygwin@cygwin.com
> Subject: RE: GDB always receives sigsegv with cygwin 1.3.13-2
> 
> 
> Both.
> 
> > -----Original Message-----
> > From: Christopher Faylor [mailto:cgf@redhat.com]
> > Sent: Wednesday, October 16, 2002 11:36 AM
> > To: cygwin@cygwin.com
> > Subject: Re: GDB always receives sigsegv with cygwin 1.3.13-2
> > 
> > 
> > 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:      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/
> 
> 

--
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/

Re: GDB always receives sigsegv with cygwin 1.3.13-2

[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://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: GDB always receives sigsegv with cygwin 1.3.13-2

[Rolf Campbell]

> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com] 
> 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 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.
I'm using the GUI version of GDB.  The sigsegv is shown in a
message-box, with an option "Don't show this again." (or something like
that), and an OK button.  After I click the ok button, that's when it
locks up for a while.  I don't know how to get the backtrace from GDB's
sigsegv.

> 
> 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.

I'm using the GUI version of GDB.  So, the console is not a Dos-box or
rxvt, and none of the key combinations that I can think of did anything
(Ctrl+Insert, ^C).  After selecting text, Ctrl+Insert pastes it back
into the console window but seems to have no effect on the Win32
clipboard.

I tried running gdb --nw and this is what happened (this program runs
fine outside gdb with any cygwin dll, and it worked in gdb with the old
dll):
/c>gdb --nw /c/node.10/node/local-objs/tools/hc12/S2Raw/S2Raw.exe
GNU gdb 2002-07-19-cvs (cygwin-special)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) set args a b
(gdb) run
Starting program: /c/node.10/node/local-objs/tools/hc12/S2Raw/S2Raw.exe
a b

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 cygwin_premain3 ()
#2  0x61083a7d in _libkernel32_a_iname ()
#3  0x61083ae6 in _libkernel32_a_iname ()
#4  0x61083b30 in _libkernel32_a_iname ()
#5  0x61082989 in _libkernel32_a_iname ()
#6  0x610852c5 in _libkernel32_a_iname ()
#7  0x61085409 in _libkernel32_a_iname ()
#8  0x0040f520 in __register_frame_info_bases ()
#9  0x0040f568 in __register_frame_info ()
#10 0x0040105f in __do_frame_init ()
#11 0x61005ed5 in _libkernel32_a_iname ()
#12 0x61007a1b in _libkernel32_a_iname ()
#13 0x004010da in main (numArgs=3, args=0xa010fc0) at S2Raw.cc:30
#14 0x61007549 in _libkernel32_a_iname ()
#15 0x6100780d in _libkernel32_a_iname ()
#16 0x004123c2 in cygwin_crt0 ()
#17 0x0040103c in mainCRTStartup ()
#18 0x77e9ca90 in _libkernel32_a_iname ()

--
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/

Re: GDB always receives sigsegv with cygwin 1.3.13-2

[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 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/

RE: GDB always receives sigsegv with cygwin 1.3.13-2

[Rolf Campbell]

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@redhat.com] 
> Sent: Wednesday, October 16, 2002 12:26 PM
> To: cygwin@cygwin.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/

RE: GDB always receives sigsegv with cygwin 1.3.13-2

[Rolf Campbell]

Both.

> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com] 
> Sent: Wednesday, October 16, 2002 11:36 AM
> To: cygwin@cygwin.com
> Subject: Re: GDB always receives sigsegv with cygwin 1.3.13-2
> 
> 
> 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:      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/

Re: GDB always receives sigsegv with cygwin 1.3.13-2

[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:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: GDB always receives sigsegv with cygwin 1.3.13-2

[Rolf Campbell]

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:cgf@redhat.com] 
> Sent: Tuesday, October 15, 2002 7:41 PM
> To: cygwin@cygwin.com
> 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/

Re: GDB always receives sigsegv with cygwin 1.3.13-2

[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 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/

GDB always receives sigsegv with cygwin 1.3.13-2

[Rolf Campbell]

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.

I don't know if this is a problem with gdb, or with cygwin (maybe the
new malloc?).

-Rolf

--
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/