From owner-freebsd-hackers Sun Aug 12 10:15:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5268137B409; Sun, 12 Aug 2001 10:15:04 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA16703; Sun, 12 Aug 2001 13:14:15 -0400 (EDT) Date: Sun, 12 Aug 2001 13:14:15 -0400 (EDT) From: Daniel Eischen To: David Malone Cc: Michael Robinson , hackers@freebsd.org, current@freebsd.org Subject: Re: _sigprocmask in malloc.c causes full file table? In-Reply-To: <20010812165829.A16568@salmon.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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, 12 Aug 2001, David Malone wrote: > 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? I don't think so. It's hard to imagine how you would install a signal handler without having the threads library initialized first (sigaction is wrapped and initializes the threads library if it hasn't been already). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message