Re: [perl #127138] NativeCall not thread safe?

2016-01-04 Thread Bartłomiej Palmowski
I've already corrected myslef (but somehow my second email didn't make it to the bugtracker), so I'll repeat it here: Actually getenv isn't thread safe but rakudo shouldn't crash anyway. Here is another example: $ cat foo.c #include int foo(void) { return 0; } $ gcc -fPIC -shared foo.c -o

[perl #127138] NativeCall not thread safe?

2016-01-04 Thread via RT
# New Ticket Created by Bartłomiej Palmowski # Please include the string: [perl #127138] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127138 > Hi, recently when trying to parallelise fetching multiple websites with

Re: [perl #127138] NativeCall not thread safe?

2016-01-04 Thread Brandon Allbery
On Mon, Jan 4, 2016 at 10:51 AM, Elizabeth Mattijsen wrote: > > getenv should be threadsafe according to: > > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_09_01 > > > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/getenv.html > >

Re: [perl #127138] NativeCall not thread safe?

2016-01-04 Thread Elizabeth Mattijsen
> On 03 Jan 2016, at 21:20, Bartłomiej Palmowski (via RT) > wrote: > > # New Ticket Created by Bartłomiej Palmowski > # Please include the string: [perl #127138] > # in the subject line of all future correspondence about this issue. > #