This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.5.18: ld command generates stackdump
OK. This time gdb seemed to attach to the broken ld process, but the
back trace still doesn't have symbols...
GNU gdb 6.3.50_2004-12-28-cvs (cygwin-special)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
welcome to change it and/or distribute copies of it under certain
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
This GDB was configured as "i686-pc-cygwin"...
Attaching to program `/bin/ld.exe', process 3028
[Switching to thread 3028.0x604]
#0 0x7c901231 in ntdll!DbgUiConnectToDbg ()
#1 0x7c9507a8 in ntdll!KiIntSystemCall ()
#2 0x00000005 in ?? ()
#3 0x00000004 in ?? ()
#4 0x00000001 in ?? ()
#5 0x195dffd0 in ?? ()
#6 0x74617453 in ?? ()
#7 0xffffffff in ?? ()
#8 0x7c90ee18 in strchr () from /cygdrive/c/WINDOWS/system32/ntdll.dll
#9 0x7c9507c8 in ntdll!KiIntSystemCall ()
#10 0x00000000 in ?? () from
It looks like my new version of ld is in /bin and /usr/bin.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html