> Nitin Sane Wrote:
> > On Fri, Mar 16, 2001 at 06:52:26PM +0100, Richard Guenther wrote:
> > > Well, using pthreads and forking in them seems to trigger libc
> > > bugs (read: SIGSEGvs) here under certain conditions (happens,
> > > after I introduced signal handlers and using pthread_sigmask,
> >
On Fri, Mar 16, 2001 at 06:52:26PM +0100, Richard Guenther wrote:
> Well, using pthreads and forking in them seems to trigger libc
> bugs (read: SIGSEGvs) here under certain conditions (happens,
> after I introduced signal handlers and using pthread_sigmask,
> I think), so hangs should be definite
: fork and pthreads
On Fri, Mar 16, 2001 at 06:52:26PM +0100, Richard Guenther wrote:
> Well, using pthreads and forking in them seems to trigger libc
> bugs (read: SIGSEGvs) here under certain conditions (happens,
> after I introduced signal handlers and using pthread_sigmask,
>
Hi!
Well, using pthreads and forking in them seems to trigger libc
bugs (read: SIGSEGvs) here under certain conditions (happens,
after I introduced signal handlers and using pthread_sigmask,
I think), so hangs should be definitely possible, too...
Richard.
On Fri, 16 Mar 2001 [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
> I am having a strange problem.
>
> I have a big daemon program to which I am trying to add multi-threading.
>
> At the begining, after some sanity check, this program does a double fork to
> create a deamon.
>
> After that it listens for the client on the port. When
I am having a strange problem.
I have a big daemon program to which I am trying to add multi-threading.
At the begining, after some sanity check, this program does a double fork to
create a deamon.
After that it listens for the client on the port. Whenever the client
connects, it creates a new
6 matches
Mail list logo