[openbeosnetteam] Testing Problems

I downloaded the entire net_kit tree again today and recompiled and installed 
everything and got some interesting results from the test apps (see below).  
I was wondering why test2 started at thread #2, so I went into the source and 
put in some print statements for testing.  When I tried to compile it, I got 
the message "no more semaphores".  I did a bunch more testing, including 
about 20 reboots and I found that test2 and test3 don't seem to affect the 
system, but when I run test1, I run out of semaphores and my system croaks.  
It doesn't freeze up, but I can't even run things like "ls". I didn't turn on 
any debugging yet, but I was wondering if maybe this is a known problem or is 
it just me?  I am running 5.03 (non-bone, non-Dano) and have 256M RAM, so I 
know I'm not running out of memory or anything like that. 

$ test1
Thread 1, starting test...
Thread 2, starting test...
Failed! Socket could not be created.
Error was -2147483648 [No memory]
This was after I had created 3019 sockets
Failed! Socket could not be created.
Error was -2147483648 [No memory]
This was after I had created 3022 sockets
Test complete.           

$ test2
===================================
= Socket creation and bind() test =
===================================
Thread 2, starting test...
Error: Socket couldn't be created
Code: -2147483648
Desc: No memory   

$ test2
===================================
= Socket creation and bind() test =
===================================
Thread 2, starting test...
Error: Socket couldn't be created
Code: -2147483648
Desc: No memory   

$ gcc -o test2 test2.c
gcc: installation problem, cannot exec 
`/boot/develop/tools/gnupro/lib/gcc-lib/i586-beos/2.9-beos-991026/cpp': No 
more semaphores  
$ make
make: vfork: No more semaphores
$

Other related posts: