Can"t get "kill "INT", $pid;" to work on 5.8.8

This is a multi-part message in MIME format.

--===============1295891994==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C761CF.E03B4CBA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C761CF.E03B4CBA
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Folks,

=20

I don't seem to be able to get any kind of signaling to work on 5.8.8
build 820.=20

Has anyone else ran into a similar situation? If so did you find a work
around?

=20

I have tried

Kill "INT", $pid;

=20

The target process never makes it into the $SIG{INT} handler when this
is done. Manually entering CTRL-C works as expected and does get into
the signal handler.

=20

On 5.6.1 we obtained a console handle and used:

$console->GenerateCtrlEvent();

=20

This also does not work on 5.8.8.

=20

The only information I can find in the porting document is that signals
now wait for the last opcode to complete before processing the signal. I
don't think that's the issue here as the signal is never received or
processed in the first place.

=20

Any information would be appreciated.

=20

Thanks - Rick

=20

=20

Rick Washburn

928-478-4663, Cell 928-978-1798

=20


------_=_NextPart_001_01C761CF.E03B4CBA
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable




charset=3Dus-ascii">

Re: Can"t get "kill "INT", $pid;" to work on 5.8.8

Washburn, Frederick wrote:
> Hi Folks,
> =

> I don=92t seem to be able to get any kind of signaling to work on 5.8.8 =

> build 820.

There are no signals in Win32 if that's what we're talking about. AS has
implemented a pseudo signal mechanism that can be blocked on wait mode IO
and therefore is hardly reliable. Personally I wouldn't even attempt to
use signals of any sort other than maybe attempting cleanup on Ctrl-C abort.

> Has anyone else ran into a similar situation? If so did you find a work =

> around?
> =

> I have tried
> =

> Kill =93INT=94, $pid;

It would be: kill 'INT', $pid; kill is case sensitive.

Where did you get $pid from - what mechanism ?
What is the $pid process doing when you kill it ? Is it blocked ?
Where is some actual test code that shows the problem ?

I just attempted a similar test and it killed the process OK - note that
the other process wasn't doing any blocking IO and also not that was
on 811 not 820, but if you have failing 820 test code I'd be glad to help
verify it fails (or not) on 811.

> The target process never makes it into the $SIG{INT} handler when this =

> is done. Manually entering CTRL-C works as expected and does get into =

> the signal handler. =


That implies that the target process has a console, but not much else
and Ctrl-C doesn't really use signals on Windoze.
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs