From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12957 invoked from network); 11 Jan 2000 09:14:44 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 11 Jan 2000 09:14:44 -0000 Received: (qmail 4984 invoked by alias); 11 Jan 2000 09:14:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9288 Received: (qmail 4977 invoked from network); 11 Jan 2000 09:14:37 -0000 Date: Tue, 11 Jan 2000 10:14:22 +0100 (MET) Message-Id: <200001110914.KAA26671@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk CC: John Harres In-reply-to: John Harres's message of Mon, 10 Jan 2000 21:59:55 -0700 Subject: Re: zsh 3.0.7 coredump John Harres wrote: > I vaguely remember hearing something about this, but in searching the > archives I have found nothing. > > I seem to be having a problem with zsh handling signals causing > coredumps. It seems as if a process being run under zsh gets a signal, it > triggers a zsh coredump. I'm using 3.0.7 on Solaris 8 beta. > > After forcing a coredump of a running process, zsh coredumps as > well. Please let me know if there's anything further I can provide to help > diagnose this. I can't reproduce this with 3.1.6++. An exact recipe and a stack trace of a debugging-compiled shell (so that we can find out which strlen() is called with a zero argument) would be helpful. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de