[Starkit] Starpack/XOTcl/Thread exit behavior

[sgargash at comcast.net]

I'm seeing a difference in behavior between starpack'd code vs the 
same code running unpacked (on Windows XP), especially with 
respect to process termination.  Are there any known differences 
in behavior?

(This is a copy of my post to comp.lang.tcl)

I've got a problem where I get different behavior with a starpack vs.
running the same code (& interpreter) unpacked.

My code launches a thread for handling a device.  The device is managed
by an XOTcl object, and it registers an XOTcl setExitHandler to save
its state out to a data file on exit.

This code all works fine when I run out of the source tree, but when I
build it into a starpack, it ceases to function correctly.  When I exit
from the starpack, the data file is touched but it has no contents.

The problem is kind of funky. I've tried, but so far I've been unable
to reduce it down to a simple test case.   I've googled around, but
haven't been able to find anything interesting. Is there any known
differences in behavior between the way a starpack terminates threads
vs the way an interpreter would terminate the thread?  Or any known bad
interactions between XOTcl and starpacks and threads?

As I've run into a bit of an impasse, even some debugging suggestions
would useful,  Thanks.