From: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
To: "Jon A. Christopher" <jon@amanda.tamu.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: bug in getenv/putenv on linuxppc/G4
Date: 01 Nov 1999 13:55:24 +0100 [thread overview]
Message-ID: <kfyd7tuz803.fsf@kieraypc01.p.y.ki.era.ericsson.se> (raw)
In-Reply-To: "Jon A. Christopher"'s message of "Mon, 1 Nov 1999 02:02:55 -0600 (EST)"
"Jon A. Christopher" <jon@amanda.tamu.edu> writes:
> I've just discovered a bug in either getenv (probably) or putenv (less
> likely) on linuxppc on a G4, glibc-2.1.1-6c.
>
> The attached test program demonstrates the bug. Basically, using putenv
> to add a variable to the environment whose name is only one letter long
> and then using getenv to read it doesn't work.
>
> Variables with two or more letters are processed as normal.
>
> I'm not sure if this is a glibc or a linuxppc problem, but I don't have
> teh same problem on my intel RH 5.2 box, or any other unix I've ever heard
> of.
It's a libc problem, reported on the libc-alpha list a few months
ago, and I think a patch was posted too.
It's fixed in glibc 2.1.2 in any case.
//Marcus
--
-------------------------------+------------------------------------
Marcus Sundberg | http://www.stacken.kth.se/~mackan/
Royal Institute of Technology | Phone: +46 707 295404
Stockholm, Sweden | E-Mail: mackan@stacken.kth.se
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-11-01 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-01 8:02 bug in getenv/putenv on linuxppc/G4 Jon A. Christopher
1999-11-01 12:55 ` Marcus Sundberg [this message]
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=kfyd7tuz803.fsf@kieraypc01.p.y.ki.era.ericsson.se \
--to=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
--cc=jon@amanda.tamu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.