|
From: Rex J. <re...@lv...> - 2001-11-02 06:30:42
|
I just checked in some code to deal with GDI handles. At least a few things remain to be done: When a process exits, a win32k function will need to be called that will clean up all outstanding handles in the table. This can be called from GDI32 DLL rundown I think. I used a fast mutex to protect access to the table. Is this a reasonable sync object to use across processes? GDI handles keep the process id as a field, but PsGetCurrentProcess does not seem to be available to a kernel mode dll. Which function is available that returns the current process id? Accoring to all I can find, GDI handles (and GDI functions) are not thread safe. So I removed all the code that was locking and unlocking individual handles. I originally added the handle locking code based on a hint from Wine. However, is code involving User handles expected to be thread safe? I dont see how if the underlying GDI calls are not, but its possible. If so we cannot reuse the GDI handle routines for User handles as I would like to. Rex Jolliff re...@lv... ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |