[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: Bug in thread code
From: |
Marcel Stadtmann |
Subject: |
AW: Bug in thread code |
Date: |
Thu, 2 Jan 2003 11:09:55 -0000 |
Hello Albert,
Thanks for your help. But i think this is not the real problem.
Maybe my discribtion was not correct. On the sample, the thread will start,
do his job, and then terminate. For me means this, the resource of this thread
should be
free after termination. Is this not correct ?? Are there still resources
allocated ??
Happy New YEAR
Marcel
-----Ursprüngliche Nachricht-----
Von: Albert Strasheim [mailto:address@hidden
Gesendet: Mittwoch, 1. Januar 2003 16:44
An: Marcel Stadtmann
Cc: address@hidden
Betreff: Re: Bug in thread code
Hello,
On Tue, 31 Dec 2002, Marcel Stadtmann wrote:
> I found a bug in the thread code section. (Used Version GNU Common
> C++ '2' 1.0.7) After starting abount 1024 thread's, i got the
> errorcode 11.
Error 11 seems be EAGAIN. It is returned by pthread_create when not
enough system resources to create a process for the new thread are
available, or more than PTHREAD_THREADS_MAX (16384 on my system)
threads are already active.
I am not surprised that starting 1024 threads causes this error. To
compare, my system is currently only running about 66 processes in
total.
It might be possible to start this many threads using the new pthreads
implementation that the RedHat folks are working on (also requires a
recent 2.5.x kernel), but any design requiring 1024 threads probably
still requires some rethinking.
Cheers,
Albert
- AW: Bug in thread code,
Marcel Stadtmann <=