[Tcl-bugs] [ tcl-Bugs-1939509 ] Tcl hangs in "exec" (on multi-processor machines)

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

Bugs item #1939509, was opened at 2008-04-10 16:34
Message generated for change (Settings changed) made by dkf
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1939509&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: 24. Channel Commands
>Group: current: 8.5.2
Status: Open
Resolution: None
>Priority: 9
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Andreas Kupries (andreas_kupries)
Summary: Tcl hangs in "exec" (on multi-processor machines)

Initial Comment:
Sender: Wolfgang Schmid
        Siemens AG
        Munich, Germany
E-Mail: Wol...@si...
Phone:  +49 89 636 41098


"Tclsh83" and "tclsh85" hang in exec command, if running on multiprocessor platforms. (The test program is running on a Windows-2003-Server with 2 Dual-Core-Xeons without HyperThreading.)


That's our test environment:

("load,bat" runs "tclsh85" with the script "testexec.tcl" in an endless; "testexec.tcl" starts 5 times a program (Dos-Batch-Script) using "exec" command; the DOS-Batch-Script simply does "exit 0"))

	load.bat: (to be called from DOS prompt):
	=========
		:loop

		D:\Tcl8.5.0\bin\tclsh85.exe clock.tcl	>> trace.txt

		D:\Tcl8.5.0\bin\tclsh85.exe testexec.tcl

		goto loop


	testexec.tcl:
	=============

		set fd [open "traceexec.txt" "w"]

		puts $fd "\ncallexec 1 started"
		flush $fd

		set status [catch { exec ./callexec.bat p1 p2 } outcmd]

		puts $fd "status: $status, result: $outcmd"
		puts $fd "callexec 1 terminated"
		flush $fd


		# 5 times the same stuff as above


		close $fd
		exit 0



	callexec.bat:	Batch-Script that does nothing:
	=============  

		@echo off

		rem echo "callproc started" >> callproc.txt

		exit 0


Two trace file will be created:
- trace.txt 
     contains time stamps when "tclsh85" is started
- traceexec.txt
     contains loggings that "callexec.bat" was running and the appropriate exit codes


After a short time (15 - 20 minutes), "tclsh85" hangs.
("No more trace entries are written to "trace.txt")

Is there a chance of fining the error in Tcl8.3 ?

Feel free to contact me via e-mail if information is missing.

Regards,
Wolfgang


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

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