I have a piece of code that is behaving badly. Unfortunately I didnt write it and I dont have access to the source code, just the OBJ. The problem is that this code is leaking handles and I need to close them post facto. Is there a method for enumerating the allocated handles so that I can check their state and close them if they are signalled?
Last edited by abachler; 10-29-2007 at 12:42 PM.
sysinternals.com have tools that "dig around in the kernel", such as "Process Explorer". I'm not sure if this is:
1. exactly what you want
2. roughly what you want
3. not at all what you want
But I think it's worth getting for the odd occasion when some application says "I can't open <filename> because it's locked", and it turns out that some cruddy app has that file open - you can FORCE close the file from Process Explorer.
You can also look at all sorts of handles in it, so it may help you.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Interesting, but Ill have to go with option 3. What I need is a way to programmatically enumerate the handles, so I can close them from my application.
You'll have to use the undocumented (NT)ZwQuerySystemInformation and (NT)ZWQueryObject functions.What I need is a way to programmatically enumerate the handles
thx
complete code posted on news://comp.os.ms-windows.programmer.win32
a long time ago...
ah usenet, those were the days.
