Skip Menu |
 

This queue is for tickets about the JSPL CPAN distribution.

Report information
The Basics
Id: 81404
Status: open
Priority: 0/
Queue: JSPL

People
Owner: sog [...] msg.com.mx
Requestors: wolfix57 [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: JSPL doesn't want to work with Coro module
Date: Sat, 24 Nov 2012 17:38:25 +0400
To: bug-JSPL [...] rt.cpan.org
From: Sergey Volkov <wolfix57 [...] gmail.com>
Download (untitled) / with headers
text/plain 1.1k
Hi! I need to run JSPL inside of Coro, but JSPL doesn't want to work with it... #!/usr/bin/perl use JSPL; use Coro; async { my $rt = JSPL::Runtime->new(); my $ctx = $rt->create_context; print "done"; }->join(); I can't even create JSPL context inside of Coro thread, I always get "Segmentation fault" error. Is that a kind of bug or something? P.S. I wrote also to Marc Lehman (the creator of Coro module), maybe that could help, it's a reply from him: ---------- Hi - not all modules are threadsafe. You'd need to find out why it crashes to see whats going wrong. For example, by making a backtrace. Since what seems to crash is JSPL, you could also just send a bugreport (or a enhancement request with this info to the JSPL developers - they should know better what they are doing and what needs to be done to work with threads. Show quoted text
> Is that a kind of bug or something?
It's either a bug or, more likely, simply an incompatibility. Most likely, JSPL makes nonportable assumptions about the stack and requires a backend for each new platform or environment. ---------------------- ---------------------- By the way, I want to thank you for your work! I love JSPL so much... if it can only be thread-safe..
Subject: Re: [rt.cpan.org #81404] JSPL doesn't want to work with Coro module
Date: Sat, 24 Nov 2012 18:58:20 -0600
To: bug-JSPL [...] rt.cpan.org
From: Salvador Ortiz Garcia <sog [...] msg.com.mx>
Download (untitled) / with headers
text/plain 1.9k
Sergey, Thank you for your report. In fact the JSPL context is created, try changing "print" with "warn" to avoid the buffering. The segfault occurs at context's destruction time, when the scope ends, but deep inside SpiderMonkey, I need to dig into it. Salvador. On 11/24/2012 07:30 AM, Sergey Volkov via RT wrote: Show quoted text
> Sat Nov 24 08:30:54 2012: Request 81404 was acted upon. > Transaction: Ticket created by wolfix57@gmail.com > Queue: JSPL > Subject: JSPL doesn't want to work with Coro module > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: wolfix57@gmail.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=81404 > > > > Hi! I need to run JSPL inside of Coro, but JSPL doesn't want to work > with it... > > #!/usr/bin/perl > > use JSPL; > use Coro; > > async { > > my $rt = JSPL::Runtime->new(); > my $ctx = $rt->create_context; > print "done"; > }->join(); > > I can't even create JSPL context inside of Coro thread, > I always get "Segmentation fault" error. > > Is that a kind of bug or something? > > > P.S. I wrote also to Marc Lehman (the creator of Coro module), maybe > that could help, it's a reply from him: > ---------- > > Hi - not all modules are threadsafe. You'd need to find out why it crashes > to see whats going wrong. For example, by making a backtrace. > > Since what seems to crash is JSPL, you could also just send a bugreport > (or a enhancement request with this info to the JSPL developers - they > should know better what they are doing and what needs to be done to work > with threads. >
>> Is that a kind of bug or something?
> It's either a bug or, more likely, simply an incompatibility. Most likely, > JSPL makes nonportable assumptions about the stack and requires a backend > for each new platform or environment. > > > ---------------------- > ---------------------- > > By the way, I want to thank you for your work! > I love JSPL so much... if it can only be thread-safe.. > >


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.