|
2026-10-20
| ||
| 10:21 | • Closed ticket [67fd4f973a]: incorrect results of 'info exists' when unse... artifact: 72d2c52686 user: jan.nijtmans | |
|
2026-10-19
| ||
| 18:15 | • Ticket [845241ffff] Unsetting env vars in slave interps status still Open wi... artifact: c397ba3d05 user: serhiy.storchaka | |
| 18:15 | • Ticket [67fd4f973a] incorrect results of 'info exists' when unset env va... artifact: 1bb724274c user: serhiy.storchaka | |
| 18:15 | • Ticket [3602289fff] EnvTraceProc errors when env var doesn't exist statu... artifact: 133bdc6dae user: serhiy.storchaka | |
| 18:12 | Fix [3602289fff], [67fd4f973a] and [845241ffff]: after another interp unset an env variable, a read ... closed check-in: f1438aeb70 user: serhiy.storchaka tags: env-stale-element | |
|
2019-05-20
| ||
| 17:48 | • New ticket [67fd4f973a] incorrect results of 'info exists' when unset en... artifact: 9dd3b3bc54 user: GrAnd | |
| Ticket UUID: | 67fd4f973ac46efd5999060ce4aafd4e0093a0a5 | ||
| Title: | incorrect results of 'info exists' when unset env var in one interp and check for existence from another interp | ||
| Type: | Bug | Created on: | 2019-05-20 17:48:50 |
| Submitter: | GrAnd | Assigned to: | jan.nijtmans |
| Subsystem: | 17. Commands I-L | Severity: | Severe |
| Priority: | 5 Medium | Last modified: | 2026-10-20 10:21:00 |
| Status: | Closed | Closed by: | jan.nijtmans |
| Resolution: | Duplicate | Closed on: | 2026-10-20 10:21:00 |
| Version: | 8.6.18, 9.0.5, 9.1.0 | ||
| Description: | ||||
|
There are 2 interpreters main and slave. If I do "set ::env(FOO) bar", it appears in both interps ("info exists ::env(FOO)" reports 1 and I can actually read the var. Then, if I do "unset ::env(FOO)" in any interp, this var fully disappears in that interp ("info exists ::env(FOO)" returns 0 and on read an error is generated). But, in another interp "info exists ::env(FOO)" still claims that the var exists (returns 1), but if I actually try to read that variable I get an error. Test script: #!/bin/bash #\ exec tclsh "$0" And the output of script above: TCL version: 8.7a1 | ||||
| User Comments: | ||||
serhiy.storchaka added on 2026-10-19 18:15:21:
Still present in 8.6, 9.0 and 9.1. The env read trace returns an error for a name no longer in the environment, but keeps the stale element, so [info exists] still sees it. Proposed fix in branch env-stale-element, together with [3602289fff] and [845241ffff]: the read trace removes the stale element. Test env-11.3. jan.nijtmans added on 2026-10-20 10:21:00:
Dup of [845241ffff] | ||||
