From: SourceForge.net <no...@so...> - 2004-06-30 07:38:45
|
Bugs item #982547, was opened at 2004-06-30 09:38 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 Category: 16. Commands A-H Group: obsolete: 8.4.1 Status: Open Resolution: None Priority: 5 Submitted By: Patrick Samson (p_samson) Assigned to: Donal K. Fellows (dkf) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |
From: SourceForge.net <no...@so...> - 2004-06-30 09:32:45
|
Bugs item #982547, was opened at 2004-06-30 08:38 Message generated for change (Settings changed) made by dkf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 >Category: 24. Channel Commands Group: obsolete: 8.4.1 Status: Open Resolution: None Priority: 5 Submitted By: Patrick Samson (p_samson) >Assigned to: Andreas Kupries (andreas_kupries) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |
From: SourceForge.net <no...@so...> - 2004-07-19 09:34:03
|
Bugs item #982547, was opened at 2004-06-30 00:38 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 Category: 24. Channel Commands Group: obsolete: 8.4.1 Status: Open Resolution: None Priority: 5 Submitted By: Patrick Samson (p_samson) Assigned to: Andreas Kupries (andreas_kupries) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 02:34 Message: Logged In: NO We reproduce this problem very often. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |
From: SourceForge.net <no...@so...> - 2004-07-19 15:35:21
|
Bugs item #982547, was opened at 2004-06-30 00:38 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 Category: 24. Channel Commands Group: obsolete: 8.4.1 Status: Open Resolution: None Priority: 5 Submitted By: Patrick Samson (p_samson) Assigned to: Andreas Kupries (andreas_kupries) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 08:35 Message: Logged In: NO I could reproduce this problem very easily with TclTk 8.3.2 by calling for instance exec pv.exe in an loop If I started 3 to 4 jobs of this kind in parallel it used to hang TclTk interpretors within minutes! According to my tests done today, it seems to be ok with TclTk 8.4.6.1. I cross the fingers and hope it can continue like this for a few days... So you should check your installed TclTk version ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 02:34 Message: Logged In: NO We reproduce this problem very often. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |
From: SourceForge.net <no...@so...> - 2004-07-19 18:38:11
|
Bugs item #982547, was opened at 2004-06-30 00:38 Message generated for change (Comment added) made by hobbs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 Category: 24. Channel Commands Group: obsolete: 8.4.1 >Status: Pending >Resolution: Out of Date Priority: 5 Submitted By: Patrick Samson (p_samson) Assigned to: Andreas Kupries (andreas_kupries) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- >Comment By: Jeffrey Hobbs (hobbs) Date: 2004-07-19 11:38 Message: Logged In: YES user_id=72656 appears to be fixed in recent releases then. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 08:35 Message: Logged In: NO I could reproduce this problem very easily with TclTk 8.3.2 by calling for instance exec pv.exe in an loop If I started 3 to 4 jobs of this kind in parallel it used to hang TclTk interpretors within minutes! According to my tests done today, it seems to be ok with TclTk 8.4.6.1. I cross the fingers and hope it can continue like this for a few days... So you should check your installed TclTk version ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 02:34 Message: Logged In: NO We reproduce this problem very often. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |
From: SourceForge.net <no...@so...> - 2004-07-21 12:02:32
|
Bugs item #982547, was opened at 2004-06-30 09:38 Message generated for change (Comment added) made by p_samson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 Category: 24. Channel Commands Group: obsolete: 8.4.1 >Status: Open Resolution: Out of Date Priority: 5 Submitted By: Patrick Samson (p_samson) Assigned to: Andreas Kupries (andreas_kupries) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- >Comment By: Patrick Samson (p_samson) Date: 2004-07-21 14:02 Message: Logged In: YES user_id=994002 Unfortunately I'm running a Cygwin version of TCL. So I'm stuck to the current 8.4.1 package until the maintainer builds a more recent one. Thanks for your comments. Make me feel I'm not mad or alone in this world :) (nobody), who couldn't reproduce the pb with 8.4.6.1 anymore, please confirm after a long time run of your case test (with these aleatory pb, you're never sure). Meanwhile, I'm redesigning the sources to avoid exec as much as possible. ---------------------------------------------------------------------- Comment By: Jeffrey Hobbs (hobbs) Date: 2004-07-19 20:38 Message: Logged In: YES user_id=72656 appears to be fixed in recent releases then. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 17:35 Message: Logged In: NO I could reproduce this problem very easily with TclTk 8.3.2 by calling for instance exec pv.exe in an loop If I started 3 to 4 jobs of this kind in parallel it used to hang TclTk interpretors within minutes! According to my tests done today, it seems to be ok with TclTk 8.4.6.1. I cross the fingers and hope it can continue like this for a few days... So you should check your installed TclTk version ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 11:34 Message: Logged In: NO We reproduce this problem very often. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |
From: SourceForge.net <no...@so...> - 2005-10-05 23:17:57
|
Bugs item #982547, was opened at 2004-06-30 00:38 Message generated for change (Settings changed) made by andreas_kupries You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&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: obsolete: 8.4.1 >Status: Pending Resolution: Out of Date Priority: 5 Submitted By: Patrick Samson (p_samson) Assigned to: Andreas Kupries (andreas_kupries) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- Comment By: Patrick Samson (p_samson) Date: 2004-07-21 05:02 Message: Logged In: YES user_id=994002 Unfortunately I'm running a Cygwin version of TCL. So I'm stuck to the current 8.4.1 package until the maintainer builds a more recent one. Thanks for your comments. Make me feel I'm not mad or alone in this world :) (nobody), who couldn't reproduce the pb with 8.4.6.1 anymore, please confirm after a long time run of your case test (with these aleatory pb, you're never sure). Meanwhile, I'm redesigning the sources to avoid exec as much as possible. ---------------------------------------------------------------------- Comment By: Jeffrey Hobbs (hobbs) Date: 2004-07-19 11:38 Message: Logged In: YES user_id=72656 appears to be fixed in recent releases then. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 08:35 Message: Logged In: NO I could reproduce this problem very easily with TclTk 8.3.2 by calling for instance exec pv.exe in an loop If I started 3 to 4 jobs of this kind in parallel it used to hang TclTk interpretors within minutes! According to my tests done today, it seems to be ok with TclTk 8.4.6.1. I cross the fingers and hope it can continue like this for a few days... So you should check your installed TclTk version ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-07-19 02:34 Message: Logged In: NO We reproduce this problem very often. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |
From: SourceForge.net <no...@so...> - 2005-10-20 02:21:01
|
Bugs item #982547, was opened at 06/30/04 00:38 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&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: obsolete: 8.4.1 >Status: Closed Resolution: Out of Date Priority: 5 Submitted By: Patrick Samson (p_samson) Assigned to: Andreas Kupries (andreas_kupries) Summary: exec doesn't return sometimes Initial Comment: OS: Windows/Cygwin I have a script running regularly (every 5 mn), with this command: if {[catch {eval exec "bash --login file.tcl $dbname $table $dirlog"} errmsg]} { puts ... } else { puts ... } It can run perfectly for days, but sometimes, as this morning (05:20 AM, so no activity), the command freezes and doesn't return. No puts is executed. The bash process has done its work, I can see that its last instruction (a puts) is executed, and there is no more sh or pgtclsh process anymore. It seems as if exec didn't detect the end of execution of this argument and still waits. It may be a race condition, so I can not reproduce it at will, nor provide a test case, sorry. Anyway, I submit the bug report for the record, and in the hope it may ring a bell for the exec command maintainer. Some "me too" are welcome as well. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 10/19/05 19:20 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Patrick Samson (p_samson) Date: 07/21/04 05:02 Message: Logged In: YES user_id=994002 Unfortunately I'm running a Cygwin version of TCL. So I'm stuck to the current 8.4.1 package until the maintainer builds a more recent one. Thanks for your comments. Make me feel I'm not mad or alone in this world :) (nobody), who couldn't reproduce the pb with 8.4.6.1 anymore, please confirm after a long time run of your case test (with these aleatory pb, you're never sure). Meanwhile, I'm redesigning the sources to avoid exec as much as possible. ---------------------------------------------------------------------- Comment By: Jeffrey Hobbs (hobbs) Date: 07/19/04 11:38 Message: Logged In: YES user_id=72656 appears to be fixed in recent releases then. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 07/19/04 08:35 Message: Logged In: NO I could reproduce this problem very easily with TclTk 8.3.2 by calling for instance exec pv.exe in an loop If I started 3 to 4 jobs of this kind in parallel it used to hang TclTk interpretors within minutes! According to my tests done today, it seems to be ok with TclTk 8.4.6.1. I cross the fingers and hope it can continue like this for a few days... So you should check your installed TclTk version ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 07/19/04 02:34 Message: Logged In: NO We reproduce this problem very often. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=982547&group_id=10894 |