[Tcl-bugs] [ tcl-Bugs-930530 ] env-multiple FAILED env variables

[SourceForge.net <no...@so...>]

Bugs item #930530, was opened at 2004-04-06 11:02
Message generated for change (Comment added) made by tauvan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=930530&group_id=10894

Category: 08. Environment Variables
Group: current: 8.4.6
Status: Open
Resolution: None
Priority: 5
Submitted By: tauvan (tauvan)
Assigned to: Jim Ingham (wolfsuit)
Summary: env-multiple FAILED env variables

Initial Comment:
as local only (notRoot)

machine: mac ppc G4 (1st PCI 400Mhz) OSX 10.1.5
for additional info see:
 [910323] 20 failures with 8.4.6 on MacOS X 10.3, many env 
related

---- Result was:
__CF_USER_TEXT_ENCODING=0x1F5:0:0
---- Result should have been (exact matching):

==== env-2.1 FAILED


---- Result was:
NAME1=test string
__CF_USER_TEXT_ENCODING=0x1F5:0:0
---- Result should have been (exact matching):
NAME1=test string
==== env-2.2 FAILED


---- Result was:
NAME1=test string
NAME2=more
__CF_USER_TEXT_ENCODING=0x1F5:0:0
---- Result should have been (exact matching):
NAME1=test string
NAME2=more
==== env-2.3 FAILED


---- Result was:
NAME1=test string
NAME2=more
XYZZY=garbage
__CF_USER_TEXT_ENCODING=0x1F5:0:0
---- Result should have been (exact matching):
NAME1=test string
NAME2=more
XYZZY=garbage
==== env-2.4 FAILED


---- Result was:
NAME1=test string
NAME2=new value
XYZZY=garbage
__CF_USER_TEXT_ENCODING=0x1F5:0:0
---- Result should have been (exact matching):
NAME1=test string
NAME2=new value
XYZZY=garbage
==== env-3.1 FAILED


---- Result was:
NAME1=test string
XYZZY=garbage
__CF_USER_TEXT_ENCODING=0x1F5:0:0
---- Result should have been (exact matching):
NAME1=test string
XYZZY=garbage
==== env-4.1 FAILED


---- Result was:
XYZZY=garbage
__CF_USER_TEXT_ENCODING=0x1F5:0:0
---- Result should have been (exact matching):
XYZZY=garbage
==== env-4.2 FAILED


---- Result was:
__CF_USER_TEXT_ENCODING=0x1F5:0:0
§=¶
---- Result should have been (exact matching):
§=¶
==== env-4.3 FAILED


---- Result was:
__CF_USER_TEXT_ENCODING=0x1F5:0:0
§=§
---- Result should have been (exact matching):
§=§
==== env-4.4 FAILED


---- Result was:
__CF_USER_TEXT_ENCODING=0x1F5:0:0
¶=§
---- Result should have been (exact matching):
¶=§
==== env-4.5 FAILED


support data:
 when from shell(SHELL=/bin/tcsh) "env"
 both local and root have "__CF_USER_TEXT_ENCODING=
0x1F5:0:0"

 unset env($name) removes everything
 prior to tests "PATH" is added
 in "proc getenv" prior to "exec" only "PATH"
 when running "printenvScript" prior to any executions
   as local ONLY "__CF_USER_TEXT_ENCODING" is added to env

my conclusion:
 OSX has a bug or tcsh does, my bet is on the OSX.
 possible solution:
  add to "printenvScript":

    if {$tcl_platform(os) == "Darwin"} {
	lrem names __CF_USER_TEXT_ENCODING
    }	

Thanks;
Steven

----------------------------------------------------------------------

>Comment By: tauvan (tauvan)
Date: 2004-05-17 15:02

Message:
Logged In: YES 
user_id=1011552

  More info: unset env($name) outside printenvScript
These are based on what is inside test:

if   foreach ... puts "$p=$env($p)"  ok
if   exec /bin/tcsh << env  ok
if   exec /...../build/tcltest << $printenvScript
        returns __CF_USER_TEXT_ENCODING=0x1F5:0:0
if   exec /bin/sh << env
        returns ...HOME, PWD, LOGNAME, SHLVL, _

Not sure what's happening in execvp may have to do
with environ
Default shell is /bin/tcsh
Any pointers you may have would help.


----------------------------------------------------------------------

Comment By: tauvan (tauvan)
Date: 2004-05-11 15:05

Message:
Logged In: YES 
user_id=1011552

  More info:
the error depends on the location of
unset env($name).
if unset is outside the script an error occurs
if unset is placed inside the script no error

----------------------------------------------------------------------

Comment By: tauvan (tauvan)
Date: 2004-05-07 15:13

Message:
Logged In: YES 
user_id=1011552

  New info:
I created a file "printenv" which I renamed "printenv2" to make
sure no conflict with printenv.
  From tclsh shell:
% exec /Users/steven/Desktop/tclproj/build/tcltest /Users/steven/
Desktop/tclproj/build/printenv2
  Result:
Exact match to test result. No __CF_USER_TEXT_ENCODING.

Could this be a result of "catch"? I keep looking, but if I'm missing
something please let me know.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=930530&group_id=10894