Can you check whether the Tcl_Obj triggering this panic is an empty
string in "pure unicode" form? There's a gap in UpdateStringOfString
not checking for that case, but all the paths which should be able to
create it appear to have string rep creation covered.
It would be best to get this reported in the actual Tcl Bug Tracker
at Sourceforge, and include whatever you can about the value that
triggers the panic. Its contents and history.
| Don Porter Mathematical and Computational Sciences Division |
| XXXX@XXXXX.COM Information Technology Laboratory |
~DPorter/ NIST |