zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: ZSH Workers Mailing List <zsh-workers@sunsite.dk>
Subject: Re: Almost all tests pass under new cygwin
Date: Tue, 22 May 2001 16:44:42 +0100	[thread overview]
Message-ID: <3B0A896A.26BD1352@u.genie.co.uk> (raw)
In-Reply-To: <1010522153140.ZM22170@candle.brasslantern.com>

Bart Schaefer wrote:
> 

> Same answer I just gave Jason Price:  make check with ZTST_verbose=2
> so we can tell which zmodload command dies.

It is the very last zmodload in the loop which does zmodload -i for
every module it found in config.modules (the `for m in $mods' loop).
I've gone through typing the zmodload commands manually and it is always
the last one which causes the segfault regardless of the order in which
they are loaded.

Oliver


  reply	other threads:[~2001-05-22 15:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 15:14 Andrej Borsenkow
2001-05-22 15:24 ` Andrej Borsenkow
2001-05-22 15:31 ` Bart Schaefer
2001-05-22 15:44   ` Oliver Kiddle [this message]
2001-05-23 16:51     ` About zmodload test segfaults Bart Schaefer
2001-05-24 12:15       ` Andrej Borsenkow
2001-05-25 16:54         ` PATCH: Block device tests Bart Schaefer
2001-05-26  8:24           ` Andrej Borsenkow
2001-05-27 22:54             ` Bart Schaefer
2001-05-28  6:50               ` Andrej Borsenkow
2001-05-28 16:06                 ` Bart Schaefer
2001-05-28 17:25                   ` Bart Schaefer
2001-05-29 10:34                   ` Peter Stephenson
2001-05-29 10:51                     ` Andrej Borsenkow
2001-05-29 15:37                       ` Bart Schaefer
2001-05-30  9:21                         ` Peter Stephenson
2001-05-28  9:21       ` About zmodload test segfaults Sven Wischnowsky
2001-05-22 15:53   ` Almost all tests pass under new cygwin Andrej Borsenkow
2001-05-23 11:40 ` Peter Stephenson

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=3B0A896A.26BD1352@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --cc=zsh-workers@sunsite.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).