public inbox for
 help / color / mirror / Atom feed
From: Laura Arhire <>
Subject: Re: strange pthread_create cap
Date: Thu, 03 Sep 2009 06:41:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <001c01ca2bfb$147ad3a0$3d707ae0$>


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 

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!).


      parent reply	other threads:[~2009-09-03  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 10:49 Laura Arhire
2009-09-02 14:28 ` Ross Johnson
2009-09-02 14:36   ` Ross Johnson
2009-09-02 18:28   ` robert kindred
2009-09-02 23:53     ` John E. Bossom
2009-09-03  6:41     ` Laura Arhire [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).