zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: FPATH/autoload still strange in -dev-21
Date: Thu, 6 Apr 2000 12:49:10 +0200 (MET DST)	[thread overview]
Message-ID: <200004061049.MAA06636@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Thu, 6 Apr 2000 09:51:41 +0000


Bart Schaefer wrote:

> ...
>
> } I'm not sure any more if this is really a race condition. I suspect a
> } memory corruption of some kind, triggered by importing $FPATH from the 
> } environment (which would also explain why I can't reproduce, with
> } different allocation behaviours and all that).
> 
> And the memory corruption ... steps on the exit status of the subshell as
> returned to the parent, somehow?  I can't see how that could be ... the
> subshell is calling _exit(0) but the parent still takes the false branch.
> Hrm.

I was thinking about something that messes up some memory used
somewhere when that `if' is executed. Wild guessing, of course, but
memory problems are the only ones I can think of when thinking about
the difference between FPATH in the environment and not in the
environment.

I may be completely wrong, of course. Debugging session in execif()
could tell us something.

> } And the initial setup of fpath also depends on the site-function dirs
> } that are automatically added and so on...
> 
> I do NOT compile with --enable-function-subdirs, if that matters.

Hm. I have some default function dirs...

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2000-04-06 10:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-06 10:49 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-06  8:18 Sven Wischnowsky
2000-04-06  9:51 ` Bart Schaefer
2000-04-06 15:56   ` Zefram
2000-04-06 16:42     ` Bart Schaefer
2000-04-06 17:21       ` Zefram
2000-04-05  8:03 Sven Wischnowsky
2000-04-05  5:09 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=200004061049.MAA06636@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@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).