WIndows process table and process image.

Hi,

Please help me understand how Windows process is managed.

My application uses some utility programs such as nslookup and dnscmd.
Fo some cases my application needs to kill those child process by calling
TerminateProcess().

Here is something I cannot understand, after killing a process why the
process is still in process table but its image is gone?

I used Process explorer to check, the process is listed but its image does
not exist.

I tried windbg to connect to the process but windbg told me the process
image is not there.

The process does hold some file handles so its current directory cannot be
removed.

Is there a zambie process in Windows as unix? I cannot find any documents
about Windows Zambie processes.

Thanks,
Chris


.

Relevant Pages

  • Re: Blue screen with Event 1076
    ... windbg will download the proper symbol files ... and images of the foreign system from the ms symbol server. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... pc) of a windows 2003 terminal server on a windows xp or should I run ...
    (microsoft.public.windows.terminal_services)
  • Re: System reboots when I try to print
    ... Install Debugging Tools for Windows from Microsoft Homepage. ... I suppose if you attach to the spooler-process with F6, windbg ... I then was unable to that particular network directory. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: blue screen
    ... what is wrong is to run windbg on the dump file. ... download/install windbg from Microsoft Debugging Tools ... all windows." ... This will display a quick analysis of which driver crashed and the most ...
    (microsoft.public.windowsxp.hardware)
  • RE: Vista SP1 fails to install with BCCode: 1000008e
    ... Tools for Windows ... I did not need that driver anymore. ... There are also two open support requests to the free Vista SP1 support. ... windbg symbol path per the windbg help file. ...
    (microsoft.public.development.device.drivers)
  • Re: VB Error - update
    ... despite explicitly setting windbg as the default tool no error logs ... Since you are the only one this happened to, try re-installing Windows. ...
    (microsoft.public.vb.general.discussion)