Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<200112111452.IAA26938@devmail.dev.tivoli.com>
X-Mailer:	exmh version 2.5 07/13/2001 with nmh-1.0.4
To:	cygwin AT cygwin DOT com
Reply-To:	jheyman AT dev DOT tivoli DOT com
Subject:	env command and case sensitivity
Mime-Version:	1.0
Date:	Tue, 11 Dec 2001 09:52:21 -0500
From:	(Jerry Heyman) <jerry AT dev DOT tivoli DOT com>

I've got an user who is complaining that the env.exe
distributed with the commercial version of GNUpro (1.0)
is always showing their environment variables in uppercase.

No, they're not running inside of the GNUpro provided bash -
but from a previous version of bash that we use (problem also
exists in CMD shell).  I've confirmed that env.exe returns 
uppercase version of the variable, and that the version of bash 
is actually using it as a mixed case.

I'm assuming that the issue has to do with the run-time
environment as stepping through the env.exe with gdb shows that
things are already wrong when the program initially accesses
*envp.

Aside from upgrading GNUpro or using the supplied version of bash,
are there any clues as to why the initial load of *envp is all
set to uppercase??

Been through the faq, google, and the email archive - but either
I've missed it or the problem has not been addressed.

Thanks,

jerry
-- 
Jerry Heyman   919.224.1442    | IBM SWG/Tivoli Software |"Software is the 
Build Infrastructure Architect | 3901 S Miami Blvd       | difference between
jheyman AT dev DOT tivoli DOT com         | Durham, NC  27703       | hardware and 
reality"
                          http://www.acm.org/~heymanj



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -