| Ticket UUID: | 554117eddec7220f1cda04c16cc45a77d6c175e0 | ||
| Title: | Tcl_SaveInterpState/Tcl_RestoreInterpState are not usable to save interpreter state (error info/code) | ||
| Type: | Bug | Created on: | 2020-02-10 16:35:07 |
| Submitter: | sebres | Assigned to: | nobody |
| Subsystem: | 45. Parsing and Eval | Severity: | Minor |
| Priority: | 5 Medium | Last modified: | 2023-09-12 13:40:37 |
| Status: | Pending | Closed by: | nobody |
| Resolution: | Fixed | Closed on: | |
| Version: | |||
| Description: | ||||
|
Current implementation of This causes that system traces observing Although I know that The error is initially noticed in GH/sebres/tclclockmod/issues/19#issuecomment-582639778. But now I have a branch bug-554117edde with test cases [95db6756e8bd9f96] illustrating that. | ||||
| User Comments: | ||||
sebres added on 2020-02-10 16:44:27:
As one can see both 1.9.* test cases fails:
==== result-1.9.2 Tcl_SaveInterpState: nested save state does not modify error info/code FAILED
...
---- Result was:
0 {UNEXPERR INVISIBLE} {ERROR in safe block}
---- Result should have been (exact matching):
0 {EXPERR TEST-ERROR} {ERROR expected error}
==== result-1.9.2 FAILED
sebres added on 2020-02-10 16:52:21:
Fixed in [9cace6cc78], tests passed. jan.nijtmans added on 2023-09-12 13:40:37:
I'm seeing 3 failing test-cases: init.test | ||||
