Re: Debugger/Thread curiosity
"William DePalo [MVP VC++]" <willd.no.spam@mvps.org> wrote in message
news:eTBcrpUfGHA.3488@TK2MSFTNGP02.phx.gbl...
"Jeff Partch [MVP]" <jeffp@mvps.org> wrote in message
news:%23bWgiIUfGHA.1260@TK2MSFTNGP05.phx.gbl...
How come about once out of every 100 runs the debugger outputs the fully
qualified...
I don't know for sure.
The thread 'DXSIMPL::DXSTHREAD::DXSThread::StaticThreadProc' (0xf20) has
exited with code 0 (0x0).
...and the other 99 times just a generic...
The thread 'Win32 Thread' (0xf20) has exited with code 0 (0x0).
Hmm.
Does it mean I've got things horribly wrong?
I doubt it. Rather I _think_ that something is setting the "name" of the
thread as described here:
http://msdn2.microsoft.com/en-us/library/xcb2z8hs.aspx
FWIW and AFAIK, Win32 doesn't define a name attribute for threads, the
RaiseException() hack is strictly a convenience for debugging
multi-threaded applications.
Thanks, Will. I can assure you that nothing in my code does anything to set
the thread name, and I can't see how the OS would be doing it, so it must be
the debugger. It just seems odd to me that it does it so infrequently -- and
thus a tad bit worrisome. Since no one else has said anything I guess it's
not some race-something or premature-something or
cart-before-the-horse-something. Guess I'll leave it at that. :)
--
Jeff Partch [VC++ MVP]