zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <schizo@debian.org>
To: 245974-forwarded@bugs.debian.org
Cc: zsh-workers@sunsite.dk, Christian Anthon <anthon@kohn.kiku.dk>
Subject: Re: Bug#245974: zsh: export LC_ALL=da_DK causes segfault
Date: Sun, 2 May 2004 20:27:22 -0400	[thread overview]
Message-ID: <20040503002722.GA15956@scowler.net> (raw)
In-Reply-To: <20040427092356.GA4780@kohn.kiku.dk>

> > Okay, if you use a different prompt (walters, for example), it won't
> > segfault.  Correct?
> 
> Yep.
> #0  0x080a5cdf in ztrftime ()
> #1  0x08098fc4 in promptexpand ()
> #2  0x08098330 in promptexpand ()
> #3  0x402e5b8f in zleread () from /usr/lib/zsh/4.2.0/zsh/zle.so

Seems that when LC_TIME (or LC_ALL or LANG) is set to a locale such as
da_DK or de_DE, wherein am_pm is set to null strings, zsh will segfault
upon prompt-expanding %p or %P.  Seems that the first argument to
ztrftime() is often either NULL or 0x51, though I can't figure out why.


       reply	other threads:[~2004-05-03  0:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040426144112.87B951C02C@kohn.kiku.dk>
     [not found] ` <20040426154922.GA8375@scowler.net>
     [not found]   ` <20040426201800.GA2029@kohn.kiku.dk>
     [not found]     ` <20040426224229.GA12757@scowler.net>
     [not found]       ` <20040427092356.GA4780@kohn.kiku.dk>
2004-05-03  0:27         ` Clint Adams [this message]
2004-05-04  4:14           ` Clint Adams
2004-05-04  9:26             ` Peter Stephenson
2004-05-04 14:41               ` Peter Stephenson
2004-05-04 15:06                 ` Clint Adams
2004-05-04 15:30                   ` Peter Stephenson
2004-05-05  4:43                     ` Wayne Davison
2004-05-05 11:17                       ` Peter Stephenson
2004-05-04  9:50             ` Oliver Kiddle
2004-05-04 12:11               ` Clint Adams

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=20040503002722.GA15956@scowler.net \
    --to=schizo@debian.org \
    --cc=245974-forwarded@bugs.debian.org \
    --cc=anthon@kohn.kiku.dk \
    --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).