Date: Tue, 25 Jan 2000 17:25:40 -0500 (EST) From: Chuck Robey <chuckr@picnic.mat.net> To: Ilya Zakharevich <ilya@math.ohio-state.edu> Cc: Lars Eggert <larse@ISI.EDU>, perl5-porters@perl.org, current@FreeBSD.ORG Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on Message-ID: <Pine.BSF.4.21.0001251725030.315-100000@picnic.mat.net> In-Reply-To: <20000125150945.C2011@monk.mps.ohio-state.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Jan 2000, Ilya Zakharevich wrote: > 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. Do you know for a fact that perl, in the signal handler code, is not calling malloc? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- 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.BSF.4.21.0001251725030.315-100000>