Date: Sun, 12 Aug 2001 21:02:24 +0300 From: Valentin Nechayev <netch@iv.nn.kiev.ua> To: Daniel Eischen <eischen@vigrid.com> Cc: Michael Robinson <robinson@netrinsics.com>, hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: _sigprocmask in malloc.c causes full file table? Message-ID: <20010812210224.B864@iv.nn.kiev.ua> In-Reply-To: <Pine.SUN.3.91.1010812101250.25909A-100000@pcnet1.pcnet.com>; from eischen@vigrid.com on Sun, Aug 12, 2001 at 10:29:53AM -0400 References: <20010812214608.A2701@elephant.netrinsics.com> <Pine.SUN.3.91.1010812101250.25909A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sun, Aug 12, 2001 at 10:29:53, eischen (Daniel Eischen) wrote about "Re: _sigprocmask in malloc.c causes full file table?": > sigprocmask() behaves the same as pthread_sigmask(). pthread_sigmask() > needs to obtain the current thread. In obtaining the current thread, > the threads library must be initialized. In initializing the threads > library malloc() is called. Wash, rinse, repeat. > > Don't put _sigprocmask() in malloc. One can use sigprocmask() in malloc() after thread library initialized. But set of signals to block in malloc() is too application-dependent than to use such approach without bad side effects. Signal unblocking windows during event cycle seems more productive. /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010812210224.B864>