From owner-freebsd-current Tue Jan 25 12: 9:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mathserv.mps.ohio-state.edu (mathserv.mps.ohio-state.edu [128.146.111.31]) by hub.freebsd.org (Postfix) with ESMTP id 19460152BE for ; Tue, 25 Jan 2000 12:09:50 -0800 (PST) (envelope-from ilya@math.ohio-state.edu) Received: from monk.mps.ohio-state.edu (monk.mps.ohio-state.edu [128.146.111.52]) by mathserv.mps.ohio-state.edu (8.9.3+Sun/8.9.3) with ESMTP id PAA29672; Tue, 25 Jan 2000 15:09:45 -0500 (EST) Received: (from ilya@localhost) by monk.mps.ohio-state.edu (8.9.3+Sun/8.9.3) id PAA02127; Tue, 25 Jan 2000 15:09:45 -0500 (EST) Date: Tue, 25 Jan 2000 15:09:45 -0500 From: Ilya Zakharevich To: Chuck Robey Cc: Lars Eggert , perl5-porters@perl.org, current@FreeBSD.ORG Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on Message-ID: <20000125150945.C2011@monk.mps.ohio-state.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from chuckr@picnic.mat.net on Tue, Jan 25, 2000 at 02:44:05PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 02:44:05PM -0500, Chuck Robey wrote: > On Mon, 24 Jan 2000, Lars Eggert wrote: > > > Ilya, > > > > thanks for the quick response. > > > > > Signals and Perl do not mix. Please do not use signals if a segfault > > > is not a desirable form of output. > > > > Never? After reading perlipc I was under the impression that using signals > > was okay if you keep your handlers simple. I may have to use to another form > > of IPC if signals cannot be made safe. > > Our malloc can't be used in a signal handler. One can write a signal handler in such a way that no mallocs are going to be called (see my example). But this would not help: segfaults will happen anyway. Ilya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message