Strange PID 0 exception behavior on Windows

[giampaolo]

From billiej...@gmail.com on February 23, 2009 20:05:25

What steps will reproduce the problem?  
>>> psutil.Process(0).kill()
>>> psutil.Process(2408).name
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python26\Lib\site-packages\psutil\psutil.py", line 54, in __init__
    if not pid_exists(pid):
  File "C:\Python26\Lib\site-packages\psutil\psutil.py", line 149, in
pid_exists

    return _platform_impl.pid_exists(pid)
  File "C:\Python26\Lib\site-packages\psutil\_psmswindows.py", line 29, in
pid_e
xists
    return pid in _psutil_mswindows.get_pid_list()
WindowsError: [Error 87] Parametro non corretto
>>>
>>> psutil.Process(2408).name
'xchat.exe'
>>>


It seems that psutil.Process(0).kill() fails internally and that its
exception is "cached" somehow and raised when we attempt to fetch
information from another process.

Original issue: http://code.google.com/p/psutil/issues/detail?id=22

[giampaolo]

From jlo...@gmail.com on February 23, 2009 12:31:35

Fixed in r148 - kill_process() was returning 0 instead of NULL so the exception 
only being set and not raised like it should have been.

Status: Verified

[giampaolo]

From billiej...@gmail.com on February 24, 2009 15:24:40

Labels: Milestone-0.1.1

[giampaolo]

From billiej...@gmail.com on March 17, 2009 08:31:20

Status: Fixed

[giampaolo]

From g.rodola on March 02, 2013 03:44:15

Updated csets after the SVN -> Mercurial migration: r148 == revision