RE: Help... GDB no longer works after updating...

RE: Help... GDB no longer works after updating...

[Kris Erickson]

Sorry, I didn't make myself clear in my first post.  This morning I updated
everything (I step I do every couple of weeks or so).  After updating, GDB
no longer worked.  Thus, I thought one of the new updated packed broke my
GDB, so I thought I would try reverting to a previous version...  I looked
in the log and w32api and cygwin where updated, so I thought I would try
rolling them back a version.  That didn't do anything, so I tried rolling
gdb back a version.  That didn't help either.  Then I went through the
setup and forced a re-install on everything.  I am still getting the same
error...  Obviously something got messed up, but I was wondering if anyone
experienced anything like this before, before I blow away my cygwin 
installation and re-install...

Thanks for your help,

Kris

-----Original Message-----
From: Larry Hall (RFK Partners, Inc) [ mailto:lhall@rfk.com ]
Sent: Wednesday, September 19, 2001 7:23 PM
To: Kris Erickson; 'cygwin@cygwin.com'
Subject: Re: Help... GDB no longer works after updating...


What did you update?  Just selected packages or all the packages?
You mentioned specifically gdb, cygwin, w32api, and gdb but is that
all that you updated?  You should take all the packages that setup 
offers, unless you're absolutely sure that the ones you're omitting 
aren't needed by any that you're taking.  Of course, then you're 
pretty much on your own, since this list can't really support custom 
installations at this point.  If you did install all the packages, well
then I'm not sure what your issue is.  My best guess is that you have
a package synchronization issue but if you installed everything, 
synchronization is not the problem.  In that case, I can't offer any 
other ideas.

Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



At 09:03 PM 9/19/2001, Kris Erickson wrote:
>I had been happily (very happily) using GDB for debugging until this morning,
>when I decided to update my cygwin files (have to keep current).  Now GDB won't
>run anything.  I did a search on google and the cygwin lists on 
>"unknown target exception", but everything I came up with seems fairly out of
>date...
>
>Here is a simple test file I created, the error that it generates and executing
>the show command.
>
>I have tried re-installing gdb, cygwin, w32api, gcc but nothing has changed.  I
>tried going back a version in w32api and cygwin but that didn't help either...
>I really don't want to have to blow away my whole cygwin distribution because it
>took months to get X and all the nice utilities installed and compiled...
>
>Thank any of you for your help in advance,
>
>Kris
>
>cygwin session follows
>------------------------------------
>
>$ cat test.c
>#include <stdlib.h>
>
>int main(void) {
>     printf("Hello World\n");
>}
>
>Administrator@STORK ~/tmp
>$ gcc -g -o test test.c
>Administrator@STORK ~/tmp
>$ gdb -nw test.exe
>GNU gdb 5.0 (20010428-1)


<snip>

--
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: Help... GDB no longer works after updating...

[Ralf Habacker]

Kris Erickson wrote:

> I found an old cygwin1.dll (1.3.2(0.39/3/2)) I had backed up earlier
> which works.
> I also tried duplicating the error on a couple of boxes around my work and
> it seems to not be a problem on anyone elses machine (either 2000 ot
> NT).  But
> now that I know the problem is in the cygwin1.dll and not gdb or anything else
> I will take a shot at trying to find the problem.  Thanks for the pointers
> on how to debug the cygwin1.dll, I hadn't seen that before (perhaps a comment
> in the FAQ saying there are extra how-to's in the
> src/cygwin-xxx/winsup/cygwin dir)
>
I have had the same problem with cygwin 1.3.3-2 under Win2K. I have installed
cygwin 1.3.2-1
and there are no more problems with gdb. So I can confirm this statement.
Ralf

> Thanks again your help...
>
> Kris
>
> -----Original Message-----
> From: Christopher Faylor [ mailto:cgf@redhat.com ]
> Sent: Thursday, September 20, 2001 2:07 PM
> To: cygwin@cygwin.com
> Subject: Re: Help... GDB no longer works after updating...
>
>
> On Thu, Sep 20, 2001 at 02:42:11PM -0600, Mark Paulus wrote:
> >If you are having problems, and you can't debug gdb, then try this:
> >
> >Recompile/relink gdb with a -Wl,-Map -Wl,gdb.map option.  Then when you
> >get your crash message, you should be able to go back to the map file,
> >and figure out which subroutine/code segment is causing the problem.
> >Then you might be able to either desk check the code slightly, or rerun
> >gdb on gdb, and dissassemble the subroutine in question.  This should
> >allow you to get to the exact machine instruction, which will take you
> >back to the high level code involved, and then it's a matter of
> >figuring out which variable is whacked, or when/how the stack is
> >overflowing and whacking the code segment, etc, etc.
>
> You might also be able to use the techniques here:
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/how-to-
debug-cygwin.txt?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=src

to debug the application.  This would require using an older
cygwin1.dll that works, assuming that cygwin1.dll is the
problem.

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: Help... GDB no longer works after updating...

[Kris Erickson]

I found an old cygwin1.dll (1.3.2(0.39/3/2)) I had backed up earlier which works.
I also tried duplicating the error on a couple of boxes around my work and
it seems to not be a problem on anyone elses machine (either 2000 ot NT).  But 
now that I know the problem is in the cygwin1.dll and not gdb or anything else
I will take a shot at trying to find the problem.  Thanks for the pointers
on how to debug the cygwin1.dll, I hadn't seen that before (perhaps a comment
in the FAQ saying there are extra how-to's in the src/cygwin-xxx/winsup/cygwin dir)

Thanks again your help...

Kris

-----Original Message-----
From: Christopher Faylor [ mailto:cgf@redhat.com ]
Sent: Thursday, September 20, 2001 2:07 PM
To: cygwin@cygwin.com
Subject: Re: Help... GDB no longer works after updating...


On Thu, Sep 20, 2001 at 02:42:11PM -0600, Mark Paulus wrote:
>If you are having problems, and you can't debug gdb, then try this:
>
>Recompile/relink gdb with a -Wl,-Map -Wl,gdb.map option.  Then when you
>get your crash message, you should be able to go back to the map file,
>and figure out which subroutine/code segment is causing the problem.
>Then you might be able to either desk check the code slightly, or rerun
>gdb on gdb, and dissassemble the subroutine in question.  This should
>allow you to get to the exact machine instruction, which will take you
>back to the high level code involved, and then it's a matter of
>figuring out which variable is whacked, or when/how the stack is
>overflowing and whacking the code segment, etc, etc.

You might also be able to use the techniques here:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/how-to-debug-cygwin.txt?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=src

to debug the application.  This would require using an older
cygwin1.dll that works, assuming that cygwin1.dll is the
problem.

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: Help... GDB no longer works after updating...

[Christopher Faylor]

On Thu, Sep 20, 2001 at 02:42:11PM -0600, Mark Paulus wrote:
>If you are having problems, and you can't debug gdb, then try this:
>
>Recompile/relink gdb with a -Wl,-Map -Wl,gdb.map option.  Then when you
>get your crash message, you should be able to go back to the map file,
>and figure out which subroutine/code segment is causing the problem.
>Then you might be able to either desk check the code slightly, or rerun
>gdb on gdb, and dissassemble the subroutine in question.  This should
>allow you to get to the exact machine instruction, which will take you
>back to the high level code involved, and then it's a matter of
>figuring out which variable is whacked, or when/how the stack is
>overflowing and whacking the code segment, etc, etc.

You might also be able to use the techniques here:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/how-to-debug-cygwin.txt?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=src

to debug the application.  This would require using an older
cygwin1.dll that works, assuming that cygwin1.dll is the
problem.

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: Help... GDB no longer works after updating...

[Gerrit P. Haase]

Kris Erickson schrieb am 2001-09-19, 18:03:

>Here is a simple test file I created, the error that it generates and executing
>the show command.
[...]
>cygwin session follows
>------------------------------------
$ cat hello.c
#include <stdlib.h>

int main(void) {
    printf("Hello World\n");
}

>Administrator@STORK ~/tmp
>$ gdb -nw test.exe
>GNU gdb 5.0 (20010428-1)
>Copyright 2001 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) run
>Starting program: /home/administrator/tmp/test.exe
>gdb: unknown target exception 0x000006d1 at 0x77e87e08
>
>Program received signal ?, Unknown signal.
>0x77e87e08 in _libkernel32_a_iname ()
>(gdb) info target
>Symbols from "/home/administrator/tmp/test.exe".
>Win32 child process:
>        Using the running image of child thread 2808.0x7d8.
>        While running this, GDB does not access memory from...
>Local exec file:
>        `/home/administrator/tmp/test.exe', file type pei-i386.
>        Entry point: 0x401000
>        0x00401000 - 0x00401400 is .text
>        0x00402000 - 0x00402200 is .data
>        0x00403000 - 0x0040300c is .bss
>        0x00404000 - 0x00404200 is .idata

$ gdb -nw hello.exe
GNU gdb 5.0 (20010428-1)
Copyright 2001 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) run
Starting program: /home/Siebenschlaefer/script/c/hello.exe
Hello World

Program exited with code 014.
(gdb) info target
Symbols from "/home/Siebenschlaefer/script/c/hello.exe".
Local exec file:
        `/home/Siebenschlaefer/script/c/hello.exe', file type pei-i386.
        Entry point: 0x401000
        0x00401000 - 0x00401400 is .text
        0x00402000 - 0x00402200 is .data
        0x00403000 - 0x0040300c is .bss
        0x00404000 - 0x00404200 is .idata
(gdb)

Hmmm, no problems here.

Gerrit
-- 
$ uname -a
CYGWIN_NT-4.0 LORELEY 1.3.3(0.46/3/2) 2001-09-12 23:54 i686 unknown


--
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: Help... GDB no longer works after updating...

[Mark Paulus]

Well, 

If you are having problems, and you can't debug gdb,
then try this:

Recompile/relink gdb with a -Wl,-Map -Wl,gdb.map option.
Then when you get your crash message, you should be
able to go back to the map file, and figure out which 
subroutine/code segment is causing the problem.  Then
you might be able to either desk check the code slightly,
or rerun gdb on gdb, and dissassemble the subroutine in
question.  This should allow you to get to the exact
machine instruction, which will take you back to the 
high level code involved, and then it's a matter of figuring
out which variable is whacked, or when/how the stack
is overflowing and whacking the code segment, etc, etc.


On Thu, 20 Sep 2001 13:32:42 -0700, Kris Erickson wrote:

>I just backed up my c:\cygwin directory, removed it, and
>did a complete re-install and still GDB gives me an
>"unknown target exception".  Does anyone have any ideas what
>could be causing this?  I did a quick bt in GDB after it crashes 
>and I get:
>
>(gdb) run
>Starting program: /home/administrator/temp/a.exe
>gdb: unknown target exception 0x000006d1 at 0x77e87e08
>Program received signal ?, Unknown signal.
>0x77e87e08 in _libkernel32_a_iname ()
>(gdb) bt
>#0  0x77e87e08 in _libkernel32_a_iname ()
>#1  0x0022f408 in ?? ()
>#2  0x77d5895a in _libkernel32_a_iname ()
>#3  0x751511cb in _libkernel32_a_iname ()
>#4  0x751aa114 in _libkernel32_a_iname ()
>#5  0x751a8755 in _libkernel32_a_iname ()
>#6  0x61067cec in _libkernel32_a_iname ()
>#7  0x61068256 in _libkernel32_a_iname ()
>#8  0x61003d4f in _libkernel32_a_iname ()
>#9  0x6100421d in _libkernel32_a_iname ()
>#10 0x6100425c in _libkernel32_a_iname ()
>#11 0x004010bf in cygwin_crt0 ()
>    at /cygnus/netrel/src/cygwin-1.3.3-2/winsup/cygwin/lib/cygwin_crt0.c:33
>
>Can anyone help me here.  Please...
>
>Kris
> 
>
>-----Original Message-----
>From: Larry Hall (RFK Partners, Inc) [ mailto:lhall@rfk.com ]
>Sent: Wednesday, September 19, 2001 7:23 PM
>To: Kris Erickson; 'cygwin@cygwin.com'
>Subject: Re: Help... GDB no longer works after updating...
>
>
>What did you update?  Just selected packages or all the packages?
>You mentioned specifically gdb, cygwin, w32api, and gdb but is that
>all that you updated?  You should take all the packages that setup 
>offers, unless you're absolutely sure that the ones you're omitting 
>aren't needed by any that you're taking.  Of course, then you're 
>pretty much on your own, since this list can't really support custom 
>installations at this point.  If you did install all the packages, well
>then I'm not sure what your issue is.  My best guess is that you have
>a package synchronization issue but if you installed everything, 
>synchronization is not the problem.  In that case, I can't offer any 
>other ideas.
>
>Larry Hall                              lhall@rfk.com
>RFK Partners, Inc.                      http://www.rfk.com
>118 Washington Street                   (508) 893-9779 - RFK Office
>Holliston, MA 01746                     (508) 893-9889 - FAX
>
>
>
>At 09:03 PM 9/19/2001, Kris Erickson wrote:
>>I had been happily (very happily) using GDB for debugging until this morning,
>>when I decided to update my cygwin files (have to keep current).  Now GDB won't
>>run anything.  I did a search on google and the cygwin lists on 
>>"unknown target exception", but everything I came up with seems fairly out of
>>date...
>>
>>Here is a simple test file I created, the error that it generates and executing
>>the show command.
>>
>>I have tried re-installing gdb, cygwin, w32api, gcc but nothing has changed.  I
>>tried going back a version in w32api and cygwin but that didn't help either...
>>I really don't want to have to blow away my whole cygwin distribution because it
>>took months to get X and all the nice utilities installed and compiled...
>>
>>Thank any of you for your help in advance,
>>
>>Kris
>>
>>cygwin session follows
>>------------------------------------
>>
>>$ cat test.c
>>#include <stdlib.h>
>>
>>int main(void) {
>>     printf("Hello World\n");
>>}
>>
>>Administrator@STORK ~/tmp
>>$ gcc -g -o test test.c
>>Administrator@STORK ~/tmp
>>$ gdb -nw test.exe
>>GNU gdb 5.0 (20010428-1)
>
>
><snip>
>
>
>--
>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: Help... GDB no longer works after updating...

[Kris Erickson]

I just backed up my c:\cygwin directory, removed it, and
did a complete re-install and still GDB gives me an
"unknown target exception".  Does anyone have any ideas what
could be causing this?  I did a quick bt in GDB after it crashes 
and I get:

(gdb) run
Starting program: /home/administrator/temp/a.exe
gdb: unknown target exception 0x000006d1 at 0x77e87e08
Program received signal ?, Unknown signal.
0x77e87e08 in _libkernel32_a_iname ()
(gdb) bt
#0  0x77e87e08 in _libkernel32_a_iname ()
#1  0x0022f408 in ?? ()
#2  0x77d5895a in _libkernel32_a_iname ()
#3  0x751511cb in _libkernel32_a_iname ()
#4  0x751aa114 in _libkernel32_a_iname ()
#5  0x751a8755 in _libkernel32_a_iname ()
#6  0x61067cec in _libkernel32_a_iname ()
#7  0x61068256 in _libkernel32_a_iname ()
#8  0x61003d4f in _libkernel32_a_iname ()
#9  0x6100421d in _libkernel32_a_iname ()
#10 0x6100425c in _libkernel32_a_iname ()
#11 0x004010bf in cygwin_crt0 ()
    at /cygnus/netrel/src/cygwin-1.3.3-2/winsup/cygwin/lib/cygwin_crt0.c:33

Can anyone help me here.  Please...

Kris
 

-----Original Message-----
From: Larry Hall (RFK Partners, Inc) [ mailto:lhall@rfk.com ]
Sent: Wednesday, September 19, 2001 7:23 PM
To: Kris Erickson; 'cygwin@cygwin.com'
Subject: Re: Help... GDB no longer works after updating...


What did you update?  Just selected packages or all the packages?
You mentioned specifically gdb, cygwin, w32api, and gdb but is that
all that you updated?  You should take all the packages that setup 
offers, unless you're absolutely sure that the ones you're omitting 
aren't needed by any that you're taking.  Of course, then you're 
pretty much on your own, since this list can't really support custom 
installations at this point.  If you did install all the packages, well
then I'm not sure what your issue is.  My best guess is that you have
a package synchronization issue but if you installed everything, 
synchronization is not the problem.  In that case, I can't offer any 
other ideas.

Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



At 09:03 PM 9/19/2001, Kris Erickson wrote:
>I had been happily (very happily) using GDB for debugging until this morning,
>when I decided to update my cygwin files (have to keep current).  Now GDB won't
>run anything.  I did a search on google and the cygwin lists on 
>"unknown target exception", but everything I came up with seems fairly out of
>date...
>
>Here is a simple test file I created, the error that it generates and executing
>the show command.
>
>I have tried re-installing gdb, cygwin, w32api, gcc but nothing has changed.  I
>tried going back a version in w32api and cygwin but that didn't help either...
>I really don't want to have to blow away my whole cygwin distribution because it
>took months to get X and all the nice utilities installed and compiled...
>
>Thank any of you for your help in advance,
>
>Kris
>
>cygwin session follows
>------------------------------------
>
>$ cat test.c
>#include <stdlib.h>
>
>int main(void) {
>     printf("Hello World\n");
>}
>
>Administrator@STORK ~/tmp
>$ gcc -g -o test test.c
>Administrator@STORK ~/tmp
>$ gdb -nw test.exe
>GNU gdb 5.0 (20010428-1)


<snip>


--
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: Help... GDB no longer works after updating...

[Larry Hall (RFK Partners, Inc)]

What did you update?  Just selected packages or all the packages?
You mentioned specifically gdb, cygwin, w32api, and gdb but is that
all that you updated?  You should take all the packages that setup 
offers, unless you're absolutely sure that the ones you're omitting 
aren't needed by any that you're taking.  Of course, then you're 
pretty much on your own, since this list can't really support custom 
installations at this point.  If you did install all the packages, well
then I'm not sure what your issue is.  My best guess is that you have
a package synchronization issue but if you installed everything, 
synchronization is not the problem.  In that case, I can't offer any 
other ideas.

Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



At 09:03 PM 9/19/2001, Kris Erickson wrote:
>I had been happily (very happily) using GDB for debugging until this morning,
>when I decided to update my cygwin files (have to keep current).  Now GDB won't
>run anything.  I did a search on google and the cygwin lists on 
>"unknown target exception", but everything I came up with seems fairly out of
>date...
>
>Here is a simple test file I created, the error that it generates and executing
>the show command.
>
>I have tried re-installing gdb, cygwin, w32api, gcc but nothing has changed.  I
>tried going back a version in w32api and cygwin but that didn't help either...
>I really don't want to have to blow away my whole cygwin distribution because it
>took months to get X and all the nice utilities installed and compiled...
>
>Thank any of you for your help in advance,
>
>Kris
>
>cygwin session follows
>------------------------------------
>
>$ cat test.c
>#include <stdlib.h>
>
>int main(void) {
>     printf("Hello World\n");
>}
>
>Administrator@STORK ~/tmp
>$ gcc -g -o test test.c
>Administrator@STORK ~/tmp
>$ gdb -nw test.exe
>GNU gdb 5.0 (20010428-1)


<snip>


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

Help... GDB no longer works after updating...

[Kris Erickson]

I had been happily (very happily) using GDB for debugging until this morning,
when I decided to update my cygwin files (have to keep current).  Now GDB won't
run anything.  I did a search on google and the cygwin lists on 
"unknown target exception", but everything I came up with seems fairly out of
date...

Here is a simple test file I created, the error that it generates and executing
the show command.

I have tried re-installing gdb, cygwin, w32api, gcc but nothing has changed.  I
tried going back a version in w32api and cygwin but that didn't help either...
I really don't want to have to blow away my whole cygwin distribution because it
took months to get X and all the nice utilities installed and compiled...

Thank any of you for your help in advance,

Kris

cygwin session follows
------------------------------------

$ cat test.c
#include <stdlib.h>

int main(void) {
    printf("Hello World\n");
}

Administrator@STORK ~/tmp
$ gcc -g -o test test.c
Administrator@STORK ~/tmp
$ gdb -nw test.exe
GNU gdb 5.0 (20010428-1)
Copyright 2001 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) run
Starting program: /home/administrator/tmp/test.exe
gdb: unknown target exception 0x000006d1 at 0x77e87e08

Program received signal ?, Unknown signal.
0x77e87e08 in _libkernel32_a_iname ()
(gdb) info target
Symbols from "/home/administrator/tmp/test.exe".
Win32 child process:
        Using the running image of child thread 2808.0x7d8.
        While running this, GDB does not access memory from...
Local exec file:
        `/home/administrator/tmp/test.exe', file type pei-i386.
        Entry point: 0x401000
        0x00401000 - 0x00401400 is .text
        0x00402000 - 0x00402200 is .data
        0x00403000 - 0x0040300c is .bss
        0x00404000 - 0x00404200 is .idata
(gdb) show
annotate:  Annotation_level is 0.
archdebug:  Architecture debugging is 0.
args:  Argument list to give program being debugged when it is started is "".
can-use-hw-watchpoints:  Debugger's willingness to use watchpoint hardware is
    1.
case-sensitive:  Case sensitivity in name search is "auto; currently on".
check check range:  Range checking is "auto; currently off".
check type:  Type checking is "auto; currently off".
complaints:  Max number of complaints about incorrect symbols is 0.
confirm:  Whether to confirm potentially dangerous operations is on.
debug debug arch:  Architecture debugging is 0.
debug event:  Event debugging is 0.
debug expression:  Expression debugging is 0.
debug overload:  Debugging of C++ overloading is 0.
debug remote:  Debugging of remote protocol is 0.
debug serial:  Serial debugging is 0.
debug target:  Target debugging is 0.
debugevents:  Whether to display kernel events in child process is off.
debugexceptions:  Whether to display kernel exceptions in child process is off.
debugexec:  Whether to display execution in child process is off.
debugmemory:  Whether to display memory accesses in child process is off.
debugvarobj:  Varobj debugging is 0.
demangle-style:  The current C++ demangling style is "auto".
disassembly-flavor:  The disassembly flavor is "att".
---Type <return> to continue, or q <return> to quit---
download-write-size:  The write size used when downloading a program is 512.
editing:  Editing of command lines as they are typed is on.
eventdebug:  Event debugging is 0.
exec-done-display:  Notification of completion for asynchronous execution commands is off.
follow-fork-mode:  Debugger response to a program call of fork or vfork is
    "parent".
gnutarget:  The current BFD target is "auto".
height:  Number of lines gdb thinks are in a page is 25.
history history expansion:  History expansion on command input is off.
history filename:  The filename in which to record the command history is
    "/home/administrator/tmp/.gdb_history".
history save:  Saving of the history record on exit is off.
history size:  The size of the command history is 256.
input-radix:  Default input radix for entering numbers is 10.
language:  The current source language is "auto; currently c".
listsize:  Number of source lines gdb will list by default is 10.
new-console:  Creation of new console when creating child process is off.
new-group:  Creation of new group when creating child process is on.
opaque-type-resolution:  Resolution of opaque struct/class/union types (if set before loading symbols) is on.
os:  Operating system is "".
output-radix:  Default output radix for printing of values is 10.
overload-resolution:  Overload resolution in evaluating C++ functions is on.
---Type <return> to continue, or q <return> to quit---
pagination:  State of pagination is on.
print print address:  Printing of addresses is on.
print array:  Prettyprinting of arrays is off.
print asm-demangle:  Demangling of C++ names in disassembly listings is off.
print demangle:  Demangling of encoded C++ names when displaying symbols is on.
print elements:  Limit on string chars or array elements to print is 200.
print max-symbolic-offset:  The largest offset that will be printed in <symbol+1234> form is unlimited.
print null-stop:  Printing of char arrays to stop at first null char is off.
print object:  Printing of object's derived type based on vtable info is off.
print pascal_static-members:  Printing of pascal static members is on.
print pretty:  Prettyprinting of structures is off.
print repeats:  Threshold for repeated print elements is 10.
print sevenbit-strings:  Printing of 8-bit characters in strings as \nnn is
    off.
print static-members:  Printing of C++ static members is on.
print symbol-filename:  Printing of source filename and line number with <symbol> is off.
print union:  Printing of unions interior to structures is on.
print vtbl:  Printing of C++ virtual function tables is off.
prompt:  Gdb's prompt is "(gdb) ".
prompt-escape-char:  Escape character for formatting of gdb's prompt is 0.
remote remoteaddresssize:  The maximum size of the address (in bits) in a memory packet is 32.
---Type <return> to continue, or q <return> to quit---
remotebaud:  Baud rate for remote serial I/O is 4294967295.
remotebreak:  Whether to send break if interrupted is off.
remotecache:  Cache use for remote targets is off.
remotedebug:  Debugging of remote protocol is 0.
remotedevice:  Device for remote serial I/O is "".
remotelogbase:  Numerical base for remote session logging is "ascii".
remotelogfile:  Filename for remote session recording is "".
remotetimeout:  Timeout limit to wait for target to respond is 2.
scheduler-locking:  Mode for locking scheduler during execution is "off".
step-mode:  Mode of the step operation is off.
stop-on-solib-events:  Stopping for shared library events is 0.
symbol-reloading:  Dynamic symbol table reloading multiple times in one run is
    off.
unwindonsignal:  Unwinding of stack if a signal is received while in a call dummy is off.
verbose:  Verbosity is off.
watchdog:  Watchdog timer is 0.
width:  Number of characters gdb thinks are in a line is 80.
write:  Writing into executable and core files is off.

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