Thread: [OpenSTA-devel] [ opensta-Bugs-449426 ] ACQUIRE MUTEX
Brought to you by:
dansut
Menu
▾
▴
opensta-devel
|
From: SourceForge.net <no...@so...> - 2003-04-30 00:53:46
|
Bugs item #449426, was opened at 2001-08-09 04:54 Message generated for change (Settings changed) made by dansut You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=449426&group_id=10857 Category: Script Language Group: Inconvenience >Status: Pending Resolution: None Priority: 3 Submitted By: Harjot S. Hayre (hhayre) Assigned to: Geoff Hall (ghall) Summary: ACQUIRE MUTEX Initial Comment: When modelling a selected script with the Acquire Mutex, a message appears once you haave compiled a script stating "Object Acmutex not defined (at least in that context)". Thisa is more of an informative message as using acquire mutex is not really applicable in a single user replay. However the message is a little misleading. ---------------------------------------------------------------------- Comment By: Richard Clarke (rclarke) Date: 2001-11-19 09:17 Message: Logged In: YES user_id=82309 A message of this form will be logged if there is no execute method for the specified object class. This may be legitimate, for example, in the case of the Acquire and Release Mutex commands, there is no implmentation for the execute method in 'standalone' (i.e. Script Modeler replay) mode - the commands are effectively ignored in this mode. The code (in TRecord.cpp) has been changed so that a message is only written if the code is built in DEBUG mode. Changes yet to be committed to CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=449426&group_id=10857 |
|
From: SourceForge.net <no...@so...> - 2003-05-11 01:31:03
|
Bugs item #449426, was opened at 2001-08-09 08:54 Message generated for change (Comment added) made by ghall You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=449426&group_id=10857 Category: Script Language Group: Inconvenience >Status: Closed >Resolution: Fixed Priority: 3 Submitted By: Harjot S. Hayre (hhayre) Assigned to: Geoff Hall (ghall) Summary: ACQUIRE MUTEX Initial Comment: When modelling a selected script with the Acquire Mutex, a message appears once you haave compiled a script stating "Object Acmutex not defined (at least in that context)". Thisa is more of an informative message as using acquire mutex is not really applicable in a single user replay. However the message is a little misleading. ---------------------------------------------------------------------- >Comment By: Geoff Hall (ghall) Date: 2003-05-11 01:30 Message: Logged In: YES user_id=81187 The change mentioned in the previous comment is included in 1.4.x releases. ---------------------------------------------------------------------- Comment By: Richard Clarke (rclarke) Date: 2001-11-19 14:17 Message: Logged In: YES user_id=82309 A message of this form will be logged if there is no execute method for the specified object class. This may be legitimate, for example, in the case of the Acquire and Release Mutex commands, there is no implmentation for the execute method in 'standalone' (i.e. Script Modeler replay) mode - the commands are effectively ignored in this mode. The code (in TRecord.cpp) has been changed so that a message is only written if the code is built in DEBUG mode. Changes yet to be committed to CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=449426&group_id=10857 |
|
From: SourceForge.net <no...@so...> - 2006-10-04 21:23:35
|
Bugs item #1570977, was opened at 2006-10-04 23:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1570977&group_id=10857 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: Documentation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jerome Delamarche (trickyjer) Assigned to: Nobody/Anonymous (nobody) Summary: ACQUIRE MUTEX Initial Comment: The SCL Manual says "ACQUIRE MUTEX" is used for inter- script synchronization. It also says the Timeout value is in seconds. It appears that: - ACQUIRE MUTEX works also to synchronize threads (and fortunately it works !) - the Timeout value is dependent of the WAIT UNIT instruction - the ON TIMEOUT GOTO and ON ERROR GOTO clauses are mandatory to avoid a "TOF error" at runtime ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1570977&group_id=10857 |
|
From: SourceForge.net <no...@so...> - 2007-10-17 18:49:13
|
Bugs item #1570977, was opened at 2006-10-04 16:23 Message generated for change (Comment added) made by velivis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1570977&group_id=10857 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: Documentation Group: None Status: Open >Resolution: Works For Me Priority: 5 Private: No Submitted By: Jerome Delamarche (trickyjer) Assigned to: Nobody/Anonymous (nobody) Summary: ACQUIRE MUTEX Initial Comment: The SCL Manual says "ACQUIRE MUTEX" is used for inter- script synchronization. It also says the Timeout value is in seconds. It appears that: - ACQUIRE MUTEX works also to synchronize threads (and fortunately it works !) - the Timeout value is dependent of the WAIT UNIT instruction - the ON TIMEOUT GOTO and ON ERROR GOTO clauses are mandatory to avoid a "TOF error" at runtime ---------------------------------------------------------------------- >Comment By: Bernie Velivis (velivis) Date: 2007-10-17 13:49 Message: Logged In: YES user_id=1868094 Originator: NO The SCL manual says that ACQUIRE MUTEX is used to synchronize either scripts running on the local machine (scope local) or all scripts across all injectors (Test-wide). It works as documented. The ON TIMEOUT and ON ERROR clauses are documented as being optional and I am unable to reproduce TOF errors by omitting them. The SCL documentation in the modeler states incorrectly that units for the wait time in the ACQUIRE MUTEX command are in seconds. All my testing shows the wait time units for the ACQUIRE MUTEX command are in milliseconds regardless of WAIT UNIT (seconds or milliseconds). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1570977&group_id=10857 |
|
From: SourceForge.net <no...@so...> - 2007-10-17 18:51:09
|
Bugs item #1570977, was opened at 2006-10-04 16:23 Message generated for change (Settings changed) made by velivis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1570977&group_id=10857 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: Documentation Group: None >Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Jerome Delamarche (trickyjer) Assigned to: Nobody/Anonymous (nobody) Summary: ACQUIRE MUTEX Initial Comment: The SCL Manual says "ACQUIRE MUTEX" is used for inter- script synchronization. It also says the Timeout value is in seconds. It appears that: - ACQUIRE MUTEX works also to synchronize threads (and fortunately it works !) - the Timeout value is dependent of the WAIT UNIT instruction - the ON TIMEOUT GOTO and ON ERROR GOTO clauses are mandatory to avoid a "TOF error" at runtime ---------------------------------------------------------------------- Comment By: Bernie Velivis (velivis) Date: 2007-10-17 13:49 Message: Logged In: YES user_id=1868094 Originator: NO The SCL manual says that ACQUIRE MUTEX is used to synchronize either scripts running on the local machine (scope local) or all scripts across all injectors (Test-wide). It works as documented. The ON TIMEOUT and ON ERROR clauses are documented as being optional and I am unable to reproduce TOF errors by omitting them. The SCL documentation in the modeler states incorrectly that units for the wait time in the ACQUIRE MUTEX command are in seconds. All my testing shows the wait time units for the ACQUIRE MUTEX command are in milliseconds regardless of WAIT UNIT (seconds or milliseconds). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110857&aid=1570977&group_id=10857 |
Thanks for helping keep SourceForge clean.
X