Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199906192328.SAA28276@mercury.xraylith.wisc.edu> To: Alex cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: multithreaded portscan In-Reply-To: Your message of "Sat, 19 Jun 1999 22:43:31 +0200." <376C00F3 DOT AC8BF928 AT i-france DOT com> Date: Sat, 19 Jun 1999 18:28:04 -0500 From: Mumit Khan Alex writes: > i am writing a portscan and i have the following problems > connect() always return -1 > socket() always return the same socket for many threads > and i think that's why connect() always fail > but i don't know how to solve this problem > is socket() thread safe ? and what can i do to get it worked ? Cygwin b20.1 is not thread safe, and so you simply cannot expect this to work. It may work by accident, but it's not designed for it yet. There is experimental threading support in newer development snapshots (you have to build it with --enable-threads); so if you're looking for thread support, you should work with one of the dev snapshots. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com