Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

earliest injection: handle extra early threads #627

Open
derekbruening opened this issue Nov 28, 2014 · 0 comments
Open

earliest injection: handle extra early threads #627

derekbruening opened this issue Nov 28, 2014 · 0 comments

Comments

@derekbruening
Copy link
Contributor

From [email protected] on November 29, 2011 10:11:01

my earliest injection ( issue #234 ) today restores its hook immediately. there
can be super-early threads when injected from outside (including from
system itself during shutdown and other times) (and really there's nothing
special about the main thread: whoever gets to init routine first is the
initializer and will then be the DR intializer). the idea is to leave the
hook but change it to spin (or if manage to get syscall support, wait) so
we can queue up these threads until DR is fully initialized.

note that in the past we discussed ways to try and avoid any other thread
being schedulable until we were set up, via SetProcessAffinityMask(0) or
sthg, but none of those panned out

this would block windbg's thread as well and if windbg can handle that
would enable debugging at pre-Ldr-init time

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=627

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant