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)



From wolfix57 [...] gmail.com Sat Nov 24 08: 30:53 2012
MIME-Version: 1.0
X-Spam-Status: No, score=-5.97 tagged_above=-99.9 required=10 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_NEUTRAL=0.779] autolearn=ham
X-Spam-Flag: NO
content-type: text/plain; charset="utf-8"; format="flowed"
Message-ID: <50B0CDD1.9020803 [...] gmail.com>
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
X-Spam-Score: -5.97
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id 4B6DF2402D6 for <cpan-bug+JSPL [...] hipster.bestpractical.com>; Sat, 24 Nov 2012 08:30:53 -0500 (EST)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZRNrxBmknL46 for <cpan-bug+JSPL [...] hipster.bestpractical.com>; Sat, 24 Nov 2012 08:30:52 -0500 (EST)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 2292524016D for <bug-JSPL [...] rt.cpan.org>; Sat, 24 Nov 2012 08:30:50 -0500 (EST)
Received: (qmail 19582 invoked by uid 103); 24 Nov 2012 13:30:50 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 24 Nov 2012 13:30:50 -0000
Received: from mail-la0-f50.google.com (HELO mail-la0-f50.google.com) (209.85.215.50) by 16.mx.develooper.com (qpsmtpd/0.84/v0.84-167-g4ed6cab) with ESMTP; Sat, 24 Nov 2012 05:30:47 -0800
Received: by mail-la0-f50.google.com with SMTP id c1so6996628lah.9 for <bug-JSPL [...] rt.cpan.org>; Sat, 24 Nov 2012 05:30:43 -0800 (PST)
Received: by 10.152.105.33 with SMTP id gj1mr5999373lab.49.1353763843833; Sat, 24 Nov 2012 05:30:43 -0800 (PST)
Received: from [192.168.1.11] ([178.44.103.147]) by mx.google.com with ESMTPS id g3sm3553228lbm.15.2012.11.24.05.30.43 (version=SSLv3 cipher=OTHER); Sat, 24 Nov 2012 05:30:43 -0800 (PST)
Authentication-Results: hipster.bestpractical.com (amavisd-new); dkim=pass header.i= [...] gmail.com
Delivered-To: cpan-bug+JSPL [...] hipster.bestpractical.com
Subject: JSPL doesn't want to work with Coro module
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120717 Thunderbird/14.0
Return-Path: <wolfix57 [...] gmail.com>
X-RT-Mail-Extension: jspl
X-Original-To: cpan-bug+JSPL [...] hipster.bestpractical.com
X-Spam-Check-BY: 16.mx.develooper.com
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=ivO04cWZ1+qJ1qezQydu45bfOkGw5D9syqlLsBVRerI=; b=VZARcQRsBMKzBpMZYuQ16ncWV9XLRYSttK794G8288GL2IFQgzNAfKARfQVeUw+TnZ 8EJvemHllexmoWyoHpx3WqGKh/3bDufCXWMDPmQbtCKRLZY4KVzmHDex6nm6rKwxRh3S KHnPNq2QqlcTDwt9HSS+owLBUt3rkLtJGGOH8heHmUq6sN7UYEKWdigkUtaerdiKvJT6 vE53I+2MocIlZrbfBWJzMldmLct7v+hRyc/WoitqO7RW8JA6U6927ve4qUlsYhFgTiAB 4l/G8AcadAIs49XL2JF53u6rR8aKY+TfSzTAHRJZlCe43WyJxurDGHL2SovXmQ+d4hzh Sg2w==
Date: Sat, 24 Nov 2012 17:38:25 +0400
X-Spam-Level:
To: bug-JSPL [...] rt.cpan.org
Content-Transfer-Encoding: 7bit
From: Sergey Volkov <wolfix57 [...] gmail.com>
X-RT-Original-Encoding: ISO-8859-1
Content-Length: 1223
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..
From sog [...] msg.com.mx Sat Nov 24 19: 58:29 2012
MIME-Version: 1.0
X-Spam-Status: No, score=-6.899 tagged_above=-99.9 required=10 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_FAIL=0.001] autolearn=ham
In-Reply-To: <rt-3.8.HEAD-6278-1353763854-615.81404-4-0 [...] rt.cpan.org>
X-Spam-Flag: NO
References: <RT-Ticket-81404 [...] rt.cpan.org> <50B0CDD1.9020803 [...] gmail.com> <rt-3.8.HEAD-6278-1353763854-615.81404-4-0 [...] rt.cpan.org>
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
Message-ID: <50B16D2C.3040708 [...] msg.com.mx>
Content-Type: text/plain; charset=UTF-8; format=flowed
Organization: Matías Software Group
X-RT-Original-Encoding: utf-8
X-Spam-Score: -6.899
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id A4136240946 for <cpan-bug+JSPL [...] hipster.bestpractical.com>; Sat, 24 Nov 2012 19:58:29 -0500 (EST)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nU5O0anPbstV for <cpan-bug+JSPL [...] hipster.bestpractical.com>; Sat, 24 Nov 2012 19:58:27 -0500 (EST)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 806D624006F for <bug-JSPL [...] rt.cpan.org>; Sat, 24 Nov 2012 19:58:27 -0500 (EST)
Received: (qmail 29517 invoked by uid 103); 25 Nov 2012 00:58:26 -0000
Received: from x16.dev (10.0.100.26) by x1.dev with QMQP; 25 Nov 2012 00:58:26 -0000
Received: from gabriela.msg.com.mx (HELO gabriela.msg.com.mx) (200.33.54.3) by 16.mx.develooper.com (qpsmtpd/0.84/v0.84-167-g4ed6cab) with ESMTP; Sat, 24 Nov 2012 16:58:24 -0800
Received: from [200.33.54.11] (monica.msg.com.mx [200.33.54.11]) by gabriela.msg.com.mx (Postfix) with ESMTP id 84DFC9FE5E for <bug-JSPL [...] rt.cpan.org>; Sat, 24 Nov 2012 18:58:20 -0600 (CST)
Delivered-To: cpan-bug+JSPL [...] hipster.bestpractical.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2
Subject: Re: [rt.cpan.org #81404] JSPL doesn't want to work with Coro module
Return-Path: <sog [...] msg.com.mx>
X-Spam-Check-BY: 16.mx.develooper.com
X-Original-To: cpan-bug+JSPL [...] hipster.bestpractical.com
X-RT-Mail-Extension: jspl
Date: Sat, 24 Nov 2012 18:58:20 -0600
X-Spam-Level:
To: bug-JSPL [...] rt.cpan.org
Content-Transfer-Encoding: 7bit
From: Salvador Ortiz Garcia <sog [...] msg.com.mx>
RT-Message-ID: <rt-3.8.HEAD-14719-1353805110-207.81404-0-0 [...] rt.cpan.org>
Content-Length: 2021
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.