[perl #131714] [BUG] Segfault seemingly related to MVMCallCapture's gc_mark, and async

2017-07-08 Thread Justin DeVuyst via RT
On Sat, 08 Jul 2017 10:45:26 -0700, c...@zoffix.com wrote: > Does it still happen after this commit > https://github.com/rakudo/rakudo/commit/f6d4fbd24b ? > > I see you have a couple of `run`s in there which use Proc::Async under > the hood. Seems to fix it. Now I'm up against some other error

[perl #131714] [BUG] Segfault seemingly related to MVMCallCapture's gc_mark, and async

2017-07-08 Thread Zoffix Znet via RT
Does it still happen after this commit https://github.com/rakudo/rakudo/commit/f6d4fbd24b ? I see you have a couple of `run`s in there which use Proc::Async under the hood.

[perl #131714] [BUG] Segfault seemingly related to MVMCallCapture's gc_mark, and async

2017-07-08 Thread Zoffix Znet via RT
Does it still happen after this commit https://github.com/rakudo/rakudo/commit/f6d4fbd24b ? I see you have a couple of `run`s in there which use Proc::Async under the hood.

[perl #131714] [BUG] Segfault seemingly related to MVMCallCapture's gc_mark, and async

2017-07-07 Thread via RT
# New Ticket Created by Justin DeVuyst # Please include the string: [perl #131714] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131714 > I golfed it as much as I could. See Below. jdv@new-host-2 t]$ cat html_decode.pl use