Overview
Artifact ID: | b90afbe10219782e49bfc63b68fe7c00aa577122 |
---|---|
Ticket: | 0b874c344dd5331a5bc28b24f723ef8905903129
Tcl SEGV |
User & Date: | aku 2013-12-03 18:33:05 |
Changes
- icomment:
> Perspective Yes. There was actually code in the function for dealing with a possible NULL in the main iPtr->cmdFramePtr already. Given this it was considered to be possible for such a NULL to wind up in the corPtr->caller.cmdFramePtr as well. > Merging Ok. > Test(s) While accepting the possibility of a NULL winding up in the coro cmdFrame I am not sure yet how it actually happens. So, from me I have no prospects of crafting the necessary test. And yes, I do wish that Colin had taken the time to reduce his script as much as possible.
- login: "aku"
- mimetype: "text/plain"