zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Reliable zsh-3.0.0 core dump
Date: Sun, 25 Aug 1996 17:50:26 -0700	[thread overview]
Message-ID: <960825175026.ZM16431@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: Reliable zsh-3.0.0 core dump" (Aug 26,  1:59am)

On Aug 26,  1:59am, Zoltan Hidvegi wrote:
} Subject: Re: Reliable zsh-3.0.0 core dump
}
} > I can't get a core dump either if I use --enable-zsh-mem ... only with
} > the system malloc.  I hadn't tried zsh-mem before.
} 
} Did you try --enable-zsh-{debug,mem{,-debug},secure-free}?

Yes; they produced no warnings, and of course the core dump didn't
happen even with nothing more than --enable-zsh-mem, so ...

} The patch below fixes a bug which may cause that.

No such luck.  I still get a core dump.

} While testing this I
} also discovered that pipe synchronization was really necessary.

Can you say a bit about why (and maybe add a comment to the code!)?

} > In the second case, the built-in alias of run-help to man expanded before
} > help was invoked; in the first case it did not.  I think it should be
} > consistent (and I think the first case is how it should work, i.e. don't
} > expand the alias, but that's less important).
} > 
} > Or is this intentional and simply not documented?
} 
} It is half-intentional.  When the current word for completion is requested
} from the lexer alias expansion is disabled for that word which is good and
} reasonable.  The same mechanism is used by run-help.

I agree that alias expansion should be disabled for the current word; I
just think it should also be disabled for run-help no matter what word
is "current."  For run-help's purposes only the word in command position
is interesting.


-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"


  reply	other threads:[~1996-08-26  0:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199608251116.NAA00518@hzoli.ppp.cs.elte.hu>
1996-08-25 19:10 ` Bart Schaefer
1996-08-25 23:59   ` Zoltan Hidvegi
1996-08-26  0:50     ` Bart Schaefer [this message]
1996-08-26 18:36       ` Zoltan Hidvegi
1996-08-18 20:31 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=960825175026.ZM16431@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@nbn.com \
    --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).