This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: gdb coredumps on any executable
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: cygwin at cygwin dot com
- Date: Thu, 25 Jan 2007 12:33:18 -0500 (EST)
- Subject: Re: gdb coredumps on any executable
- References: <Pine.GSO.4.63.0701221444550.26586@access1.cims.nyu.edu>
- Reply-to: cygwin at cygwin dot com
On Mon, 22 Jan 2007, Igor Peshansky wrote:
> On a fresh install of Cygwin, running gdb with any executable produces a
> stackdump from gdb. Here's a sample session:
>
> $ gdb /bin/test
> GNU gdb 6.5.50.20060706-cvs (cygwin-special)
> Copyright (C) 2006 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"...(no debugging symbols found)
>
> (gdb) run
> Starting program: /bin/test.exe
> Loaded symbols for /cygdrive/c/WINDOWS/system32/ntdll.dll
> Loaded symbols for /cygdrive/c/WINDOWS/system32/kernel32.dll
> Loaded symbols for /usr/bin/cygwin1.dll
> Loaded symbols for /cygdrive/c/WINDOWS/system32/advapi32.dll
> Loaded symbols for /cygdrive/c/WINDOWS/system32/rpcrt4.dll
> Loaded symbols for /usr/bin/cygintl-8.dll
> Loaded symbols for /usr/bin/cygiconv-2.dll
> Segmentation fault (core dumped)
> $ cat gdb.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at eip=0054FF55
> eax=00000000 ebx=00000000 ecx=0000006B edx=0000002F esi=00000000 edi=10259B30
> ebp=0022C148 esp=0022C0C0 program=C:\cygwin\bin\gdb.exe, pid 4296, thread main
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame Function Args
> 0022C148 0054FF55 (00000000, 006162AA, 00000008, 0022C17C)
> 0022C518 00461BE0 (00000001, 00000000, 00000000, 0000C6B0)
> 0022C648 00461F10 (00000000, 00000000, 10113C98, 00000000)
> 0022C698 00411C6B (00461EB0, 00000000, 00616290, 00000006)
> 0022C738 00463A77 (0022C7A0, FFFFFFFF, 00000000, 00000000)
> 0022C808 004271A5 (00000000, 00000000, 00000000, 0000C6B0)
> 0022C868 00427335 (FFFFFFFF, 00000000, 00000000, 00000001)
> 0022C898 00412232 (00000000, 00000001, 00000001, 00000000)
> 0022C8D8 004023C7 (100B0393, 00000001, 0022C918, 100ED570)
> 0022C918 00421C84 (100B0390, 100FB738, 0022C930, 00000000)
> 0022C948 0042221B (100ED570, 00000000, 00696ED4, 0000000C)
> 0022C968 005430E5 (0048E6D0, 00000002, 0022C998, 0048E76A)
> 0022C978 004215FB (00000000, 00000000, 00000000, 0022C900)
> 0022C998 0048E76A (00000000, 00000000, 0022C9B8, 0048E145)
> 0022C9B8 0048E1D2 (100E5440, 00000002, FFFFFFFF, 0022C9D8)
> 0022C9F8 0048EA95 (00000000, 00000000, 100FB718, 00000000)
> End of stack trace (more stack frames may be present)
> $
>
> I don't have the debugging symbols for gdb, and am unable to build one
> right now, but all of the addresses seem to be in the application space.
> The output of "cygcheck -svr" is attached.
>
> I vaguely recall such issues being redirected to the insight list, but I
> suspect this is a Cygwin problem, not a gdb one...
>
> I can build my own Cygwin, but without a working gdb it would be hard to
> debug this problem. Any ideas?
> Igor
Ping. Did this get overlooked? Can people at least confirm that this
works for them on the same setup, so I can start looking for a problem in
my local installation?
Thanks,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Freedom is just another word for "nothing left to lose"... -- Janis Joplin
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/