Hmm, OK thanks everyone!
Problem was that I had:
and although it seems to be crashing with a syntax error on the machine =
in front of me (activestate 5.8, win2K) something similar was dying =
completely on Activestate 5.6.1 on WinXP. I have just upgraded that =
machine to 5.8, so I suspect that it might have been something tickled =
Seems to be working OK now. Thanks very much everyone
From: Mattia Barbon [mailto:mattia.barbon@...]
Sent: 01 October 2003 19:04
To: Edward Wildgoose; wxperl-users@...
Subject: [wxperl-users] Re: Wx::Process::Kill problems (was: How to make
class acept events)
Il Wed, 1 Oct 2003 14:23:06 +0100 Edward Wildgoose =
<Edward.Wildgoose@...> ha scritto:
> I now have just one more really annoying issue to sort out which is
> that using wxExecuteArgs to start another perl process works fine
> (and keeping a reference to the wxProcess instance in a variable).=20
> However, calling wxProcess::Kill with the pid I got earlier is
> causing a GPF under win32 (activestate perl 5.6.1 on XP).
Works For Me (TM). I added
Wx::Process::Kill( $pid, Wx::wxSIGKILL() ); at line 102 of the
> I'm not quite sure if there is some sample code to use this anyway,
> but if there are no "known" issues with kill then I will post my
> sample for scruitiny. =20
There aren't any known issues with kill (but then, there weren't
known issues with sockets...).
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
wxperl-users mailing list