From owner-freebsd-hackers Fri Sep 19 00:45:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22181 for hackers-outgoing; Fri, 19 Sep 1997 00:45:34 -0700 (PDT) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA22176 for ; Fri, 19 Sep 1997 00:45:29 -0700 (PDT) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id JAA22469 for ; Fri, 19 Sep 1997 09:50:44 +0200 (SAT) Received: by citadel via recvmail id 22436; Fri Sep 19 09:50:14 1997 by gram.cdsec.com (8.8.5/8.8.5) id JAA01776 for hackers@freebsd.org; Fri, 19 Sep 1997 09:36:04 +0200 (SAT) From: Graham Wheeler Message-Id: <199709190736.JAA01776@cdsec.com> Subject: Re: Bug in malloc/free To: hackers@freebsd.org Date: Fri, 19 Sep 1997 09:36:03 +0200 (SAT) In-Reply-To: <19970919155813.53901@lemis.com> from "Greg Lehey" at Sep 19, 97 03:58:13 pm X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On the other hand, there's not much you can do without calling some > library routine. POSIX.1 defines "safe" routines that you can call > from a signal handler. They are: (Commercial plug) This is why every UNIX programmer should have a copy of W Richard Stevens' Advanced Programming in the UNIX Environment. A great book, which covers these sorts of issues better than any other I've seen. In fact WRS book's generally are great... Although you probably all know this anyway... -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/