/libexec/ld-elf.so.1: environment corrupt; missing value for

Hi,

(I've already posted this a few days ago, but it didn't
seem to get through to the list. I have updated the
7-current machine today, and the problem is still the
same.)

This started to happen after updating to a recent 7-current
about one week ago (it was working fine with a previous 7-
current that was a few weeks older). The shell is zsh.

zsh$ /usr/bin/su
/libexec/ld-elf.so.1: environment corrupt; missing value for
zsh$

So su(1) fails to start. Interestingly, when I first start
an sh shell, I still get the same error message, but the
shell starts anyway. Then I can use su(1) without problems:

zsh$ sh
sh: environment corrupt; missing value for
$ /usr/bin/su
Password:

It was my impression that there should be more printed in
the error message after "missing value for", so I made a
hexdump:

6e 67 20 76 61 6c 75 65 20 66 6f 72 20 1b 5b 34 |ng value for .[4|
7e 0a |~.|

Sure enough, my environment _does_ seem to be corrupt
when I look at the output of env(1): There are several
empty lines and some lines with random garbage characters
and control characters. However, after starting sh,
the garbage is gone. So sh seems to "repair" it somehow.

Is this a bug in -current's environment handling? Or is
it a bug in zsh that has only been triggered by recent
changes in FreeBSD -current?

Note that I use exactly the same zsh version and exactly
the same zsh start profiles (i.e. basically the same
environment contents) on a large number of machines,
FreeBSD and other, and this problem _only_ exists on
a recent FreeBSD 7-current.

Best regards
Oliver

PS: I'm using zsh's "allexport" option, so all shell
variables are automatically exported to the environment.
It still isn't very big; "env | wc" reports 2.5 KB.

--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd

"Whatever happened to the days when hacking started
at the cerebral cortex, and not at the keyboard?"
-- Sid on userfriendly.org by Illiad, 2007-06-20
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • /libexec/ld-elf.so.1: environment corrupt; missing value for
    ... The shell is zsh. ... my environment _does_ seem to be corrupt ... FreeBSD and other, and this problem _only_ exists on ...
    (freebsd-current)
  • Re: bash: is nested parameter expansion possible?
    ... what you're seeing in bash is rightfully considered as a bug ... >> It is not a bug, but an important part of the design of the shell ... > zsh happens to be the only shell that does just that. ...
    (comp.unix.shell)
  • Re: switching shells
    ... > 3) and needs to use arrays fairly often in scripts ... Can /sh handle arrays, or if I'm going to have arrays ... > interactive shell) I'd like to know what shell is recommended for me. ... zsh has a POSIX conformant mode that can be used to run POSIX ...
    (comp.unix.shell)
  • Re: comp.unix.shell FAQ - Answers to Frequently Asked Questions
    ... How can I generate random numbers in shell scripts? ... The zsh zmv way is ... d2u dos2unix fromdos non-standard utilities, and GNU ... works with every awk. ...
    (comp.unix.shell)
  • Re: bash vs. python scripts - which one is better?
    ... not interpreted by the shell. ... Which is why I strayed away from Perl into Python land. ... ...been on zsh for years. ... here's my script to update Mutt: ...
    (Debian-User)