Rod Butcher wrote: > That looks like what I get now from Process32First/Next. According to > the PROCESSENTRY32 structure, the 3rd value should be a ProcessID, and > the 7th should be ParentProcessID : in your example, 0 and 0, which > doesn't look good. Examples of values I got :- > 296 0 0 28 0 620 752 8 0 ProcessID=0, Parent=752 > 296 8 0 0 28 0 1504 1480 8 ProcessID=0, Parent=1504 > 296 0 28 0 864 872 6 0 0 ProcessID=28,Parent=6 > 296 28 0 304 680 8 0 0 28 ProcessID=0,Parent=0 > This appears absurd. ????? > Also, perl itself always crashes after exactly 13 calls to Process32Next > (probably on the 14th call). Plenty of RAM available, it has not > returned code 18 to indicate no more processes (anyway, there are +- 50 > running). Why would Perl itself just crash ?
How about stripping down to the bare necessities that reproduce your problem - add a use strict and use warnings to the top, run it and post the snippet and results. Then we'll all be on the same page. _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
