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/
I am analyzing a kernel dump to detect a handle leak by a particular process.
I have given a command !handle 0 7 process_address file.
This list all the file handles and i am seeing around 15k handle with the name " \Endpoint {Afd}" are being created, these are winsock handles.
I want to find the irp/thread these handles are associated, that will help me to find the exact thread in the application. Could someone provide me the commands to figure it out?
Thanks,
Sumit
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
Not sure you're going to do better than just knowing the process, nothing says there even is an active IRP or thread to track it back to. Have you tried turning on handle tracing for the process?
-scott
OSR
There is no 100% guarantee that you will pinpoint the thread that is leaking winsock handles using this approach, but you could try to run !dbgkit.ps (http://www.andreybazhan.com/dbgkit.html) command, open process's properties dialog by double clicking on the process, open threads tab and then sort by I/O Other column.