Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Aug 2001 13:14:15 -0400 (EDT)
From:      Daniel Eischen <eischen@vigrid.com>
To:        David Malone <dwmalone@maths.tcd.ie>
Cc:        Michael Robinson <robinson@netrinsics.com>, hackers@freebsd.org, current@freebsd.org
Subject:   Re: _sigprocmask in malloc.c causes full file table?
Message-ID:  <Pine.SUN.3.91.1010812130919.16081A-100000@pcnet1.pcnet.com>
In-Reply-To: <20010812165829.A16568@salmon.maths.tcd.ie>

next in thread | previous in thread | raw e-mail | index | archive | help
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-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.1010812130919.16081A-100000>