From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: stucki@math.fu-berlin.de
Cc: zsh-workers@math.gatech.edu
Subject: Re: Strange coredump in new zsh-3.0.1 on Sunos4.1.3
Date: Sat, 2 Nov 1996 23:18:27 +0100 (MET) [thread overview]
Message-ID: <199611022218.XAA00325@hzoli.ppp.cs.elte.hu> (raw)
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;
prev parent reply other threads:[~1996-11-03 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-02 15:25 C. v. Stuckrad
1996-11-02 15:30 ` Strange coredump in new zsh-3.0.1 on Sunos4.1.3 (2) C. v. Stuckrad
1996-11-02 18:21 ` Bart Schaefer
1996-11-03 15:37 ` Strange coredump in new zsh-3.0.1 on Sunos4.1.3 (FIXED) C. v. Stuckrad
1996-11-03 18:44 ` Bart Schaefer
1996-11-03 21:25 ` Zoltan Hidvegi
1996-11-02 22:18 ` Zoltan Hidvegi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199611022218.XAA00325@hzoli.ppp.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=stucki@math.fu-berlin.de \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).