|
|
sybperl-l Archive
Up Prev Next
From: michael dot peppler at bnpparibas dot com
Subject: Re: Sybperl and signals
Date: Mar 10 2006 6:11PM
There is a conflict between perl (when built in threaded mode), signals and
the Sybase _r thread-safe libraries.
Try relinking sybperl with the non-threadsafe libraries and things should
improve.
Michael
Internet
olsena@odscompanies.com@peppler.org - 10/03/2006 18:59
Sent by: owner-sybperl-l@peppler.org
To: sybperl-l
cc:
Subject: Sybperl and signals
I am getting some odd behavior trying to hook signals when ctlib is
loaded.
Here is a bit of example code written by a co-worker:
#!/usr/bin/perl
use Sybase::CTlib;
$SIG{INT}= sub {print "sigcat called with @_[0]\n"; exit;};
sleep 60;
Control-c causes a segfault with the "use Sybase::CTlib;" line and works
correctly with it commented out.
Ideas?
I am dealing with a forked program that we want to clean up correctly
when stopped by the user. (Otherwise it leaves some nasty hanging
processes around.)
--
Alan Olsen
ODS Health Plans
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
|