gdb and threads on windows.

[Ben Greear <greearb at candelatech dot com>]

For some reason, my applications shows 970 threads and is
effectively deadlocked.  This is on a windows-xp system.  The
win2k system does not appear to have this problem.  I attached
to the running process with gdb.  The backtraces for 2-970 look like
this:


Thread 7 (thread 7436.0xfe0):
#0  0x7c90eb94 in _libws2_32_a_iname ()
#1  0x7c90e9c0 in _libws2_32_a_iname ()


Thread 1 is slightly more interesting:

(gdb) bt
#0  0x7c90eb94 in _libws2_32_a_iname ()
#1  0x7c90e9c0 in _libws2_32_a_iname ()
#2  0x7c802542 in _libws2_32_a_iname ()
#3  0x5a703e6e in _libws2_32_a_iname ()
#4  0x5a70c6d0 in _libws2_32_a_iname ()
#5  0x003d2aa0 in ?? ()
#6  0xffffffff in ?? ()
(gdb) quit


I am using threads in the code, but this process never created any
threads explicitly.  Maybe something like a name resolver is 'helping' me?

Is there anything I can do to get gdb to give better backtraces?
(My app is not stripped, so symbols should be available.)

Thanks,
Ben

--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com