Home > Archive > VC Language > May 2006 > Debugger/Thread curiosity
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Debugger/Thread curiosity
|
|
| Jeff Partch [MVP] 2006-05-21, 10:09 pm |
| How come about once out of every 100 runs the debugger outputs the fully
qualified...
The thread 'DXSIMPL::DXSTHREAD::DXSThread::StaticTh
readProc' (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).
Does it mean I've got things horribly wrong?
--
Jeff Partch [VC++ MVP]
| |
| William DePalo [MVP VC++] 2006-05-21, 10:09 pm |
| "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::StaticTh
readProc' (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.
Regards,
Will
| |
| Jeff Partch [MVP] 2006-05-24, 8:09 am |
| "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...
>
> I don't know for sure.
>
>
> Hmm.
>
>
> 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]
| |
| William DePalo [MVP VC++] 2006-05-24, 7:10 pm |
| "Jeff Partch [MVP]" <jeffp@mvps.org> wrote in message
news:epCs%236yfGHA.1856@TK2MSFTNGP03.phx.gbl...
> Thanks, Will.
My pleasure.
> 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,
Right.
> so it must be the debugger.
Either that or some leftover trace statements in a library function.
> 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. :)
I know how you feel, I like my mysteries in theaters. :-)
Regards,
Will
|
|
|
|
|