From owner-freebsd-hackers Sun Aug 12 8:58:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 0F3DC37B42B; Sun, 12 Aug 2001 08:58:30 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Date: Sun, 12 Aug 2001 16:58:29 +0100 From: David Malone To: Daniel Eischen Cc: Michael Robinson , hackers@freebsd.org, current@freebsd.org Subject: Re: _sigprocmask in malloc.c causes full file table? Message-ID: <20010812165829.A16568@salmon.maths.tcd.ie> References: <20010812214608.A2701@elephant.netrinsics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from eischen@vigrid.com on Sun, Aug 12, 2001 at 10:29:53AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Aug 12, 2001 at 10:29:53AM -0400, Daniel Eischen wrote: > 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. Could this be the source of Mike's original problem with X? Maybe something that X is calling from a signal handler is resulting in the initialising of the threads library and then ends up calling malloc? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message