zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Paul Ackersviller <paulda@home.com>,
	Zsh users list <zsh-users@sunsite.auc.dk>
Subject: Re: localtraps causing core dump in 3.1.6+
Date: Sat, 29 Apr 2000 04:42:20 +0000	[thread overview]
Message-ID: <1000429044220.ZM30544@candle.brasslantern.com> (raw)
In-Reply-To: <20000428161546.A8208@tdc134.comm.mot.com>

On Apr 28,  4:15pm, Paul Ackersviller wrote:
} Subject: localtraps causing core dump in 3.1.6+
}
} I guess it's intentional now that all tests which fail in chpwd() cause
} TRAPZERR() to be executed.

Why do you guess that?  It's certainly a surprise to me.  Could you give
a more specific example of what you mean, though?  TRAPZERR() is called
any time any command exits with a nonzero status, in chpwd or anywhere
else, and as far as I can tell it always has (by coincidence, I rebuilt
zsh-2.4.306 yesterday, and TRAPZERR seems to behave the same there as in
3.0.6 and 3.1.7-pre-1).

} I recently started doing `setopt localtraps && unset -f TRAPZERR'
} because of some changes that took place for 3.1.7-pre-1.
} 
} However that led me to try the above, which dumps core
} on both 3.1.7-pre-1 and 3.1.6 when changing directory.

There is a bug in unsetting TRAPxxx (as opposed to resetting them to
something else) when localtraps is set.  You might try `trap - ZERR' or
`disable -f TRAPZERR' instead for now.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~2000-04-29  4:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-28 20:15 Paul Ackersviller
2000-04-29  4:42 ` Bart Schaefer [this message]
2000-05-01 17:13   ` TRAPZERR() in chpwd() Paul Ackersviller
2000-05-01 18:22     ` Bart Schaefer

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=1000429044220.ZM30544@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=paulda@home.com \
    --cc=zsh-users@sunsite.auc.dk \
    /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).