I've seen this bug before when the core process is trying to auto-launch cordbg. I
haven't tracked it down yet; but in most such cases there is another bug visible in
the other threads.
It would be more interesting to see the output of thread apply all backtrace (or t
a a bt abbreviated) from
Does the log file (builddf.log) have more info? If it does, can you
attach the info from it?
Pankaj
-Original Message-
From: Discussion of the Rotor Shared Source CLI implementation
[mailto:[EMAIL PROTECTED] On Behalf Of Yuan Yu
Sent: Wednesday, August 20, 2003 1:57 PM
To: [EMAIL
