Tcl Source Code

View Ticket
Login
Ticket UUID: 0c7ddf85368a7d92578e2409d0c07a09a0c5d691
Title: array variable traces don't disable additional traces on the array
Type: Bug Created on: 2019-11-02 18:18:46
Submitter: anonymous Assigned to: nobody
Subsystem: 46. Traces Severity: Minor
Priority: 5 Medium Last modified: 2019-11-02 18:18:46
Status: Open Closed by: nobody
Resolution: None Closed on:
Version: 8.6.9
Description:
When a variable trace is set on an array variable, tracing is supposed to be
disabled during the trace callback. The following test code shows that this is 
not the case.

() 1 % set ::foo(bar) one
one
() 2 % trace add variable ::foo {read write unset} traceit
() 3 % proc traceit args {puts "args=$args"; puts "ex=[info exist ::foo]"}
() 4 % set ::foo(bar)
args=::foo bar read
args=::foo {} read
ex=1
ex=1
one


While taking a quick peek at the code, it would appear that the flag for an 
arrayPtr is not getting set to indicate a trace is active. The flag is 
VAR_TRACE_ACTIVE and it is only set for an item in an array, not for the entire
 array. And so while a trace is active for an element of the array, a trace
 callback that references another member of the array or the array itself, such
 as with the [info exist] call on the array, will trigger a recursive trace 
callback which is in disagreement with the documentation.