On Sat, 8 Sep 2001, Barrie Slaymaker wrote:
> On a lot of OSs, the cwd is kept as a part of the kernel's per-process
> structures, so all threads share the same idea of cwd. Anytime you use
> a userland threads package this is likely.
we should be able to set things up so chdir() is a noop, and just adjust
the enviornent (@INC, $ENV{PATH}, open, etc) to use basename $0 instead of
'.'
> Then there's APIs that are completely non threadsafe, AFAIK, like
> setjmp/longjmp, which are used in Perl in some farily critical places.
not an issue according to sarathy..
To: Doug MacEachern <[EMAIL PROTECTED]>
Subject: Re: 5.6.1+ithreads
Date: Sun, 26 Aug 2001 23:01:48 -0700
From: Gurusamy Sarathy <[EMAIL PROTECTED]>
On Sun, 26 Aug 2001 22:22:46 PDT, Doug MacEachern wrote:
>On Sun, 26 Aug 2001, Gurusamy Sarathy wrote:
>
>> Aside from forcing the use of setjmp() instead of sigsetjmp() et al, I'm
>> not aware of any issues with setjmp(). Do you have anything more specific
>> on that?
>
>just what alan burlison has brought up on p5p:
>http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-05/msg00805.html
AFAIK, that issue only applies to sig{set,long}jmp() and is specific
to Solaris. There's no global state involved in {set,long}jmp() so
they're safe to use within the same thread. The setjmp/longjmp
reference in this page would appear to confirm this for Solaris:
http://www.sun.com/smcc/solaris-migration/docs/courses/threadsHTML/adv.html
We do ActivePerl builds here with -Ud_sigsetjmp.
Sarathy
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
