specifically, when drracket kills the thread that is expanding/transforming the program, first print out its stack trace. that way, if it is stuck somewhere, maybe we'll get a clue as to where