Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Upcoming OSR Seminars | ||
---|---|---|
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
Kernel Debugging | 30 January 2023 | Live, Online |
Developing Minifilters | 20 March 2023 | Live, Online |
Internals & Software Drivers | 17 April 2023 | Live, Online |
Writing WDF Drivers | 22 May 2023 | Live, Online |
Comments
unless someone has placed a filter driver that defers I/O
above your driver, the thread that executes the dispatch
routine is the CALLING thread.
Don Burn
----- Original Message -----
From: "Barak Mandelovich" <[email protected]>
To: "NT Developers Interest List" <[email protected]>
Sent: Sunday, March 19, 2000 12:36 PM
Subject: [ntdev] PsGetCurrentThread() question
> Hi!
>
> Here's a follow-up question, which I did not find an
> answer for in the NT-DDK:
>
> PsGetCurrentThread - does it get the thread ID for the currently
> executing thread, or does it return the thread ID of the CALLING
> process (the one that issued the ReadFile() function).
>
> In other words: Can I rely on this function to return
> the TID of the calling thread?
>
> thanks,
>
> - Barak
>
> --
> ----------------------------------------------------
> Barak Mandelovich Mercury Interactive ltd.
> [email protected] 19 Shabazi st.
> Tel: +972 3 539 9286 Yehud, 56100
> Fax: +972 3 533 1617 Israel
> ----------------------------------------------------