No, it is not a bug. The fact that the event was created in ‘kernel mode’ is
not relevant. What is important to the OS is that the event was created by
process X, and when process X terminates, all open handles associated with
all threads of process X are closed, including all the handles to your event
(unless some other application opens it before the creating process (X)
terminates.)
Spawn a worker thread and create the event using the system process. Do this
in IRP_MJ_CREATE if you so desire. The event created using the system
process will persist as long as the system process does not close the
associated handle.
-----Original Message-----
From: Daniel Simard [mailto:xxxxx@matrox.com]
Sent: Sunday, February 03, 2002 8:00 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Bug with NamedEvent in Windows2000 and
WindowsXP ?I can’t to this at DriverEntry time because, the Database of
objects is not
ready. We MUST wait until IRP_MJ_CREATE to create a
NamedEvent which is
fine when you know it.Do you thing, the fact that the user level can close an event
created at
driver level, could be a bug in Windows ? And Is there a way
to make it
fixed ?thanks
You are currently subscribed to ntdev as:
xxxxx@stratus.com To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com