[ros-bugs] [Bug 5318] CSRSS not notified of thread termination

ReactOS.Bugzilla at reactos.org ReactOS.Bugzilla at reactos.org
Thu May 6 19:07:48 CEST 2010


http://www.reactos.org/bugzilla/show_bug.cgi?id=5318


Goplat <mrnobo1024 at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Kernel                      |Win32
            Summary|Regression: Thread list     |CSRSS not notified of thread
                   |command ASSERTs after       |termination
                   |attaching to process with   |
                   |PID A0 or higher            |




--- Comment #4 from Goplat <mrnobo1024 at yahoo.com>  2010-05-06 19:07:48 CET ---
CSRSS is already notified about process termination (since that closes the
process's port handle, it gets an LPC_PORT_CLOSED message). It's thread
termination that is the problem.

Old versions of Windows apparently used to do it using a termination port:
there was a CsrNewThread function in ntdll which called
NtRegisterThreadTerminatePort. This is not a foolproof solution though, because
with the native API, you could create a thread that never calls CsrNewThread.
(Perhaps for this reason, the function is gone in Vista.) 


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



More information about the Ros-bugs mailing list