Today’s learning experience

[mithriltabby]

Microsoft Windows Hatred Status

REVILE

They obviously can’t be bothered to write useful documentation.

Today’s technical learning experience: the SuspendThread() call in Windows can return before the thread involved is actually suspended. On a fast multiprocessor machine, the “suspended” thread can actually crank out a few hundred instructions before it grinds to a halt. MSDN doesn’t tell you anything about this one way or the other.

Fortunately, I am going on vacation, and will not need to return to work until January 3, so as soon as I walk out of here tonight:

Microsoft Windows Hatred Status

IGNORE

I can pretend it’s not there.

Comments

[baronlaw.livejournal.com]

Have a nice vacation!

[mithriltabby]

That’s the plan. Large quantities of sleeping in, relaxing, and avoiding stress!

[baronlaw.livejournal.com]

Enjoy! Don't worry about all the rest of us drones buzzing away in our cubes whilst you are living the good life. ;)

[mithriltabby]

Calling GetThreadContext() (with ContextFlags = CONTEXT_CONTROL | CONTEXT_INTEGER) may be sufficient to make sure the thread is suspended. (Tip of the hat to Christopher Faylor.)