>Incidentally, the reason I couldn't check in these fixes earlier is >because they contained a rather oblivious bug. >The code in question ran Thread.Thread(0) at some point (by accident), but >the error message that this generates is devoid of any stacktrace or >source code location information. > >Would it be hard to at least log a file and line number of the offending >Thread.Thread statement?
Better now?
