If exiwhat can find your stuck process, maybe you're stuck somewhere
else, not in a connect call.
We figured it out by connecting my debugger to the stuck process
and checking the stack.
gdb will do this, maybe other debuggers too. But if you have gdb,
try this:
gdb exim process_id
This grabs the running process for debugging. Even though the executable
was not compiled for debugging, you can still see the stack. At
the gdb prompt, give the "back trace" command:
(gdb) bt
It'll display the stack. On top of mine was connect() and so Philip
knew how to fix me.
Other debuggers have other commands to find the stack.
Good luck!
Marilyn Davis, Ph.D.
eVote - online polling software for email lists
http://www.deliberate.com
marilyn@???
+1 650 965-7121 (USA)
