From: SL Baur <steve@xemacs.org>
To: zsh-workers@math.gatech.edu
Subject: A stack traceback on export LANG (where LANG is unset)
Date: 15 May 1998 02:54:26 -0700 [thread overview]
Message-ID: <m2hg2rx3jh.fsf@altair.xemacs.org> (raw)
I think zsh is choking on magic variables being exported but not
defined. I normally have LANG undefined, but use
`LANG=<something-legal> program-to-test' frequently for testing.
$ zsh -c "export fred"
$ zsh -c "export LANG"
zsh: 32244 segmentation fault (core dumped) zsh -c export LANG
Here's a better stack backtrace than the one I sent before. (The
trace is on vanilla zsh-3.1.3, gdb Src/zsh; run -c "export LANG").
Program received signal SIGSEGV, Segmentation fault.
0x807dd3e in mkenvstr (name=0x80b1628 "LANG", value=0x0) at params.c:2073
2073 *s && (*s++ != Meta || *s++ != 32); len_value++);
(gdb) where
#0 0x807dd3e in mkenvstr (name=0x80b1628 "LANG", value=0x0) at params.c:2073
#1 0x807dec7 in addenv (name=0x80b1628 "LANG", value=0x0) at params.c:2112
#2 0x8052c0a in bin_typeset (name=0x80b14d0 "export", argv=0x80b1758,
ops=0xbfffed18 "", func=21) at builtin.c:1589
#3 0x804fe28 in execbuiltin (args=0x80b1604, bn=0x8096abc) at builtin.c:352
#4 0x805d271 in execcmd (cmd=0x80b15e4, input=0, output=0, how=2, last1=1)
at exec.c:1802
#5 0x805a978 in execpline2 (pline=0x80b1734, how=2, input=0, output=0,
last1=1) at exec.c:902
#6 0x805a162 in execpline (l=0x80b15d0, how=2, last1=1) at exec.c:747
#7 0x8059dae in execlist (list=0x80b1744, dont_change_job=0, exiting=1)
at exec.c:627
#8 0x8059cba in execstring (s=0xbffff449 "export LANG", dont_change_job=0,
exiting=1) at exec.c:586
#9 0x806cb0c in init_misc () at init.c:742
#10 0x804f4ef in main (argc=3, argv=0xbffff2d4) at ./main.c:73
(gdb) print s
$1 = 0x0
Hope this helps.
reply other threads:[~1998-05-15 10:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m2hg2rx3jh.fsf@altair.xemacs.org \
--to=steve@xemacs.org \
--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).