From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16356 invoked from network); 2 Feb 2000 15:30:58 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Feb 2000 15:30:58 -0000 Received: (qmail 7892 invoked by alias); 2 Feb 2000 15:30:53 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9532 Received: (qmail 7885 invoked from network); 2 Feb 2000 15:30:53 -0000 Date: Wed, 2 Feb 2000 16:30:51 +0100 (MET) Message-Id: <200002021530.QAA11346@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: James Kirkpatrick's message of Wed, 02 Feb 2000 08:14:39 -0700 (MST) Subject: Re: Problems with trap handling? James Kirkpatrick wrote: > On Wed, 2 Feb 2000, Sven Wischnowsky wrote: > > > ... Anybody know of any other > > almost-endless loops in the code? > > I've slowly (too slowly!) been working with Bart Schaefer since around > November to determine the nature of a loop that occurs if you turn on > history files. It appears that (for example) a disconnect (hangup) causes > zsh to loop in a manner where it consumes all available memory, severely > impacting other users, until it presumably finally aborts. Putting a > TRAPHUP () { exit 1 } > works around the problem but I need to try a patch Bart sent me as well. > > Is this the sort of almost-endless loop you wanted to know about? Actually I meant loops in the C-code that are exited only under certain conditions but not because some trap handler calls break, return or continue. Hm, I think I vaguely remember the problem you described (unless you never posted it to the list, in which case I vaguely remember something completely different). Dunno if it has anything to do with the bugs I'm trying to fight... (but I don't think so, I would need to know where it hangs). Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de