From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3348 invoked by alias); 3 Sep 2009 06:41:49 -0000 Received: (qmail 3156 invoked from network); 3 Sep 2009 06:41:29 -0000 Received: from unknown (86.35.15.72) by sourceware.org with QMTP; 3 Sep 2009 06:41:29 -0000 Received: (qmail 27811 invoked from network); 3 Sep 2009 06:41:25 -0000 Received: from unknown (HELO nexus.endion-software.com) (softplus@adslexpress.ro@[89.122.51.230]) (envelope-sender ) by proxy5.romtelecom.net (qmail-ldap-1.03) with SMTP for ; 3 Sep 2009 06:41:19 -0000 Received: from [10.243.1.171] (unknown [10.243.1.171]) by nexus.endion-software.com (Postfix) with ESMTP id 64C4AB94 for ; Thu, 3 Sep 2009 09:41:17 +0300 (EEST) Message-ID: <4A9F650F.7080606@endion-software.com> Date: Thu, 03 Sep 2009 06:41:00 -0000 From: Laura Arhire User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: pthreads-win32@sourceware.org Subject: Re: strange pthread_create cap References: <4A9E4D93.5050407@endion-software.com> <4A9E80FD.3040409@homemail.com.au> <001c01ca2bfb$147ad3a0$3d707ae0$@kindred@swri.org> In-Reply-To: <001c01ca2bfb$147ad3a0$3d707ae0$@kindred@swri.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2009/txt/msg00045.txt.bz2 Hi Thanks for the replies. I managed to figure out what was wrong, and will post this here in case some else manages to do the same rookie mistake in the future. The root of the problem was that I was compiling with a memory management library. This, in turn, caused the whole non-paged pool available for my application to be allocated within the first few calls (and I suspect didn't fully release the sockets either) - actually starting threads made this obvious (simply opening/closing sockets doesn't). I had initially dismissed the memory management library as a cause because when compiling without it I still saw random test failures - so I assumed (wrongly) that there must be something I was missing in the sockets. However, while trying to figure out what resources I did not release, I fixed the bug which caused the tests to fail - so now when I do a simple compile, everything works as it should (and all the tests pass, which is a bonus!). Laura