Boost logo

Boost :

From: David Deakins (ddeakins_at_[hidden])
Date: 2007-11-22 01:43:54


It appears that if you pass the GetCurrentThread() pseudo-handle into
DuplicateHandle on WinCE, it will trigger an error rather than creating
an actual handle for the current thread. Instead, the convention on
WinCE appears to involve using the value from GetCurrentThreadId() as
the thread handle (apparently this where the ID comes from under the
hood on WinCE). Attached is a patch that substitutes this behavior in
externally_launched_thread() when building on Windows CE.

Thanks,
-Dave




Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk