You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we have code to take over unknown threads on Windows, developed for attach ( issue #725 , r2032 ), we should use it whenever we start.
We just need to call dynamorio_take_over_threads() in auto_setup(), right?
The other threads do their own initialization, so tools should be fine with it.
This would also help Cygwin support.
dynamo_start() today calls dynamorio_take_over_threads() -- and it's used
by AppInit and early injection. So just switching drinject to use
earlier injection would pick this up automatically -- except DrMem (and
probably other WinAPI-using tools) can't handle earlier injection yet.
From [email protected] on October 25, 2013 13:12:07
Xref DynamoRIO/drmemory#1355
Xref cygwin early thread problems
Xref issue #627 : early injected threads
Now that we have code to take over unknown threads on Windows, developed for attach ( issue #725 , r2032 ), we should use it whenever we start.
We just need to call dynamorio_take_over_threads() in auto_setup(), right?
The other threads do their own initialization, so tools should be fine with it.
This would also help Cygwin support.
dynamo_start() today calls dynamorio_take_over_threads() -- and it's used
by AppInit and early injection. So just switching drinject to use
earlier injection would pick this up automatically -- except DrMem (and
probably other WinAPI-using tools) can't handle earlier injection yet.
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1304
The text was updated successfully, but these errors were encountered: