Date: Sun, 12 May 2002 15:32:49 -0700 From: Mark Peek <mp@FreeBSD.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: current@FreeBSD.ORG, Poul-Henning Kamp <phk@critter.freebsd.dk> Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal Message-ID: <p05111711b9049d0b4120@[10.1.1.198]> In-Reply-To: <20020512222048.GB21019@dhcp01.pn.xcllnt.net> References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> <20020512222048.GB21019@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 3:20 PM -0700 5/12/02, Marcel Moolenaar wrote: >On Sun, May 12, 2002 at 11:27:42PM +0200, Poul-Henning Kamp wrote: >> >> It is not legal to recursively call malloc/free/realloc, and therefore >> you should either protect all calls to malloc/free/realloc by blocking >> signals or better: not call them in signal handlers. > >Ok, thanks. I guess we have a genuine tcsh(1) bug here. > >Who's maintaining tcsh? Can he/she suggest what to do or otherwise >take it from here? I've been maintaining tcsh. Can you file a PR and assign it to me? I'll follow up with the tcsh owner to resolve the problem. Mark 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?p05111711b9049d0b4120>