Closed Bug 775260 Opened 13 years ago Closed 7 years ago

debug condition/mutex calls are too verbose, should disable DEBUG_CONDITION_MUTEX

Categories

(Tamarin Graveyard :: Workers, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dschaffe, Unassigned)

References

Details

Debug shell builds are too verbose. Condition and Mutex calls output several messages. The messages are useful but we should add a command line flag to enable the messages. By default we should not be outputting this many messages. For example: output of: bug.as: import flash.concurrent.* var m:Mutex=new Mutex(); var c:Condition=new Condition(m); m.lock(); c.notify(); c.wait(1); c=new Condition(m); $ avmshell_d bug.abc thread 2021108064 calling Mutex(1).lock() thread 2021108064 acquired (1) lock thread 2021108064 calling Condition(2).notify thread 2021108064 is calling (2) state->notify with 0 waiting threads thread 2021108064 calling Condition(2).wait(1) thread 2021108064 added to (2) list thread 2021108064 releasing (1) lock thread 2021108064 is calling (1) state->notifyAll with 0 waiting threads thread 2021108064 now awake thread 2021108064 calling Condition(3).wait(10) thread 2021108064 added to (3) list thread 2021108064 releasing (1) lock thread 2021108064 is calling (1) state->notifyAll with 0 waiting threads thread 2021108064 sleeping for 10 millis (3) thread 2021108064 now awake thread 2021108064 calling unlock (1) thread 2021108064 is calling (1) state->notifyAll with 0 waiting threads thread 2021108064 acquired lock (1) during destroy
Blocks: 695061
The shell should have a command line parameter -Dverbose=workers or -Dverbose=locks to set DEBUG_CONDITION_MUTEX.
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.