Overview
| Artifact ID: | 33aa4f547299288394b93cf202d7481da90e2d5fada4cf73dd7b5a610cf963b9 |
|---|---|
| Ticket: | c6057948e5f884435ee35517008db0205f286a5e
tsv commands break thread access rules for Tcl values |
| User & Date: | sebres 2018-04-03 08:56:04 |
Changes
- icomment:
> without any regard to whether the code is running in the same thread that created that Tcl_Obj. Why it is expected? The access to the objects in the tsv-storage is mutex-protected, and each set as well as the result of any tsv-call should always contain a safe duplication of the object (thus safe for any thread). BTW I cannot reproduce the segfault with your example.
- login: "sebres"
- mimetype: "text/plain"