Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh 3.0.7 coredump
- X-seq: zsh-workers 9292
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: zsh 3.0.7 coredump
- Date: Tue, 11 Jan 2000 16:59:21 +0000
- Cc: John Harres <john.harres@xxxxxxx>
- In-reply-to: <200001110914.KAA26671@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200001110914.KAA26671@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Jan 11, 10:14am, Sven Wischnowsky wrote:
} Subject: Re: zsh 3.0.7 coredump
}
} John Harres wrote:
}
} > 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.
In particular I'd like to hear what you did to "force a coredump." It's
possible that you're causing zsh to index into a null part of the sigmsg[]
array when it's printing the reason for the core dump.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author