Date: Sat, 11 Aug 2001 16:48:43 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: Michael Robinson <robinson@netrinsics.com>, current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: _sigprocmask in malloc.c causes full file table? Message-ID: <3B75C45B.1C8A37BA@mindspring.com> References: <63889.997564604@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Sheldon Hearn wrote: > > The manual pages suck, since this should be under signal(3), not > > as a reference to sigaction(2), but... > > > > man 2 sigaction > > Some of us are so committed to improving the FreeBSD manual pages that > we even try to get something positive out of this kind of negative bait > from people who just bitch from the sidelines. > > What should we do to improve on the situation? We've already got this > in signal(3): > > See sigaction(2) for a list of functions that are considered safe for > use in signal handler. Ultimately, you'd really want the signal handler to complain when it's called by putting the whole OS into a "pedantic" mode for testing purposes (i.e.: it complains abaout the calls when they happen). This _could_ be done with shared libraries with state flags, and alternate shared library paths, but ldconfig is a barrier these days... he could have gotten the same data with a "why is this broken?" command that switched out his libraries on him, and a flag that was set when in the trampoline, and not set outside the trampoline. As for man pages, I did the manual page corrections for a couple of things, including one or two of the AIO pages, but it's really going to need a real audit. The work to do is in paraphrasing the Go SOLO 2 CDROM man pages, without violating the copyright. Really, we need some college English departments involved in having people work on this for technical writing class credit; Linux seems to have no problem attracting non-programmers... -- Terry 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?3B75C45B.1C8A37BA>