Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Strange coredump in new zsh-3.0.1 on Sunos4.1.3
- X-seq: zsh-workers 2315
- From: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
- To: stucki@xxxxxxxxxxxxxxxxx
- Subject: Re: Strange coredump in new zsh-3.0.1 on Sunos4.1.3
- Date: Sat, 2 Nov 1996 23:18:27 +0100 (MET)
- Cc: zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: <Pine.GSO.3.95.961102161204.26939J-100000@petzval> from "C. v. Stuckrad" at "Nov 2, 96 04:25:00 pm"
>
> Hi!
>
> I yesterday tried to install the new 3.0.1 including the two patches
> from the zsh-workers-list (Subjects: '4 bugs' + 'strange behaviour of autocd')
> compiled on SunOS 4.1.3 with gcc 2.7.2. Then:
>
> ONE zsh was fine (freshly logged in)
> on top of 'screen' no zhsh would survive (vers. 3.0.0 does though).
> and I get a coredump always at places like VARIABLE=`program`
> The places divver, I cud not find a 'real' system in the dumps,
> but ALWAYS it's inside the initialisation files, and always at
> an definition of a Variable. One stacktrace of gdb follows here:
You may try this patch. It fixes an obvious bug which was already present
in zsh-3.0.0 so it does not explain why zsh-3.0.0 worked.
Zoltan
*** Src/utils.c 1996/10/30 23:41:58 3.1.0.0
--- Src/utils.c 1996/11/02 22:15:19
***************
*** 913,919 ****
{
if (fd >= 0) {
fdtable[fd] = 0;
! while (!fdtable[max_zsh_fd])
max_zsh_fd--;
if (fd == coprocin)
coprocin = -1;
--- 913,919 ----
{
if (fd >= 0) {
fdtable[fd] = 0;
! while (max_zsh_fd > 0 && !fdtable[max_zsh_fd])
max_zsh_fd--;
if (fd == coprocin)
coprocin = -1;
Messages sorted by:
Reverse Date,
Date,
Thread,
Author