On Tue, Aug 12, 2003 at 04:38:44PM +0100, Avis, Ed wrote: > Tim Bunce wrote: > > [alarm(0) fails to silence SIGALRM] > > >A known problem with how Solaris handles dynamically loading a > >library that uses threads into a executable that doesn't. > > > >A probable workaround is to "use DBD::Oracle;" before the alarm() > >call. > > Yes, that fixes the problem. Do you have more details about the > Solaris bug?
Google is your friend... searching for "dbd::oracle solaris thread alarm": http://groups.google.com/groups?selm=93he36%24egc%241%40nnrp1.deja.com and on a slight tangent: http://archive.develooper.com/[EMAIL PROTECTED]/msg86656.html > I wonder whether there is anything Perl could do about > it, such as setting a flag when alarm() is called and giving a > warning if a library with threads is loaded while an alarm is active. I doubt that's practical. Tim.
