'm having a problem: any class with a
> method seems to generate an error message: "Segmentation fault (core
> dumped)" whenever a script references the class. The class (.pm6) files
> look good to me and raise no issues with the Community Edition of Comma
> IDE.
>
>
I'm trying to develop classes to replace repetitive portions of an
existing set of scripts. However, I'm having a problem: any class with a
method seems to generate an error message: "Segmentation fault (core
dumped)" whenever a script references the class. The class (.pm6)
response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently updating SetHash",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket has been
> assigned
response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently updating SetHash",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket has been
> assigned
>>> On 10 Nov 2017, at 03:28, David Lowe wrote:
>>>
>>> This crash still occurs with rakudo 2017.10.
>>>
>>> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
>>> wrote:
>>> Greetings,
>>>
>>> This message has been a
>>> On 10 Nov 2017, at 03:28, David Lowe wrote:
>>>
>>> This crash still occurs with rakudo 2017.10.
>>>
>>> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
>>> wrote:
>>> Greetings,
>>>
>>> This message has been a
s something in handling Proxy.
>
>
>> On 10 Nov 2017, at 03:28, David Lowe wrote:
>>
>> This crash still occurs with rakudo 2017.10.
>>
>> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
>> wrote:
>> Greetings,
>>
>> This message has bee
s something in handling Proxy.
>
>
>> On 10 Nov 2017, at 03:28, David Lowe wrote:
>>
>> This crash still occurs with rakudo 2017.10.
>>
>> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
>> wrote:
>> Greetings,
>>
>> This message has bee
udo 2017.10.
>
> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
> wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently updating SetHash"
udo 2017.10.
>
> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
> wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently updating SetHash"
t;
> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
> wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently updating SetHash",
> a summary
t;
> On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
> wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently updating SetHash",
> a summary
This crash still occurs with rakudo 2017.10.
On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently up
This crash still occurs with rakudo 2017.10.
On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT
wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "segmentation fault while concurrently up
It's a bit tricky to get a proper backtrace dump out of gdb for this,
but what I'm seeing is this:
this source file calls sink on a value from outside the protected lock,
which runs the FETCH of the SetHash, which calls nqp::existskey on the
internal elems hash.
That part is explosive, presumably
It's a bit tricky to get a proper backtrace dump out of gdb for this,
but what I'm seeing is this:
this source file calls sink on a value from outside the protected lock,
which runs the FETCH of the SetHash, which calls nqp::existskey on the
internal elems hash.
That part is explosive, presumably
This runs reliably when you let the lock-protected block return
something unrelated to the hash:
#!/usr/bin/env perl6
use v6.c;
my $lock = Lock.new;
my $set = SetHash.new;
await (^12).map: {
start {
for (^1000) {
$lock.protect: { $set<1> = True }
$lock.protect
This runs reliably when you let the lock-protected block return
something unrelated to the hash:
#!/usr/bin/env perl6
use v6.c;
my $lock = Lock.new;
my $set = SetHash.new;
await (^12).map: {
start {
for (^1000) {
$lock.protect: { $set<1> = True }
$lock.protect
FWIW it always did that, not a regression.
On 2017-10-05 21:10:39, j.david.l...@gmail.com wrote:
> This short program crashes reliably (with a segmentation fault) on my
> system:
>
> ```
> #!/usr/bin/env perl6
>
> use v6.c;
>
> my $lock = Lock.new;
> my $set =
# New Ticket Created by David Lowe
# Please include the string: [perl #132225]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132225 >
This short program crashes reliably (with a segmentation fault) on my
system:
```
#!/
12609785)
Ran my program and got a Segmentation Fault, even though running it multiple
times again did not trigger it. Also, got one last night with a slightly
different codebase, but one that did use two IO::Socket::Async, suggesting that
spawning several of them fast might be where the bug liv
On 04/15/2016 09:36 PM, Nicholas Clark wrote:
> multi sub cross() { }
Here's a gdb backtrace and a moarvm-level backtrace. Value looks a tiny
bit suspicious, though i don't know if there's actually anything wrong
with it.
Program received signal SIGSEGV, Segmentation fault.
0x0
On Thu, Apr 14, 2016 at 03:22:37PM -0700, Caligo Wall wrote:
> This causes segmentation fault:
>
> perl6 -e "multi sub cross() { }"
Thanks for the report.
It's an interesting failure - ASAN reports an out of bounds read:
$ ./per
# New Ticket Created by Caligo Wall
# Please include the string: [perl #127902]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127902 >
This causes segmentation fault:
perl6 -e "multi sub cross() { }"
T
# New Ticket Created by Daisuke Maki
# Please include the string: [perl #127440]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127440 >
Putting load against Crust produces a segmentation fault.
Error:
=begin
PERL6LIB=
Thanks for the report.
On Tue, Jan 12, 2016 at 02:29:46PM -0800, Alex Jakimenko wrote:
> Code:
> my $x := (my $y := $x);
> say $x.WHAT;
>
> Result:
> Segmentation fault
>
>
> Code:
> my $x := (my $y := $x);
> say $y.WHAT; # same for $y
>
> Result:
>
# New Ticket Created by Alex Jakimenko
# Please include the string: [perl #127254]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127254 >
Code:
my $x := (my $y := $x);
say $x.WHAT;
Result:
Segmentation fault
Code:
my
# New Ticket Created by Alex Jakimenko
# Please include the string: [perl #126857]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=126857 >
Code:
my ([$a]); $a.WHAT
Result:
Segmentation fault
This was found by _nadim (
h
On Tue, Oct 13, 2015 at 09:20:54AM -0700, Shoichi Kaji wrote:
> + perl6-m -Ilib -MA -e B.bar
> test.sh: line 19: 31493 Segmentation fault perl6-m -Ilib -MA -e 'B.bar'
> ```
$ ./perl6-m -Ilib -MA -e &
# New Ticket Created by Shoichi Kaji
# Please include the string: [perl #126350]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=126350 >
The following script exits with segmentation fault.
(code is also available at
ht
It seems to segfault in the op getlex when trying to locate &foo.
Moving sub foo to within the BEGIN block helps and moving it outside of A gives:
Cannot invoke this object
in method at lib/A.pm6:5
Neither the rakudo optimizer nor spesh seem to be to blame.
# New Ticket Created by Alex Jakimenko
# Please include the string: [perl #126014]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=126014 >
$ perl6 -e '"x" xx 999999'
Segmentation fault
It seems
On Sat Jan 24 14:17:53 2015, barto...@gmx.de wrote:
> The segfaults are mostly gone. Only on parrot there is a Null PMC
> Access, but only for two of the four examples. With said two examples
> there is an (non segfaulting) error on Moar and JVM as well:
>
> $ perl6 -e 'role S[::N] { N::x }' ##
On Tue Apr 14 13:00:36 2015, FROGGS.de wrote:
> moar seems happy now:
>
> $ echo -e 'my \\a = any set <1 2 3>; \n say 1 ~~ a' | ./perl6-m
> any(set(1, 2, 3))
> 0
>
> JVM still broken here, I changed the REPL's ">" to "%" to not treat it
> as a replied msg:
> $ echo -e 'my \\a = any set <1 2 3>; \
On Thu Apr 16 09:22:35 2015, FROGGS.de wrote:
> On MoarVM we get an error message instead:
> m: (1, 3, *x* ... 233)[1..4]
> rakudo-moar 67df04: OUTPUT«===SORRY!===repeat count > 1073741824
> arbitrarily unsupported...»
The JVM runs out of memory instead:
15:51 <[Coke]> r: (1, 3, *x* ... 233)[1.
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #123789]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=123789 >
m: sub foo(int:U $x) { $x };
rakudo-moar f53a94: ( no output )
m: sub foo(int:U $x) {
The segfaults are mostly gone. Only on parrot there is a Null PMC Access, but
only for two of the four examples. With said two examples there is an (non
segfaulting) error on Moar and JVM as well:
$ perl6 -e 'role S[::N] { N::x }' ## no error on Moar, Parrot and JVM
$ perl6 -e 'sub foo(::N) {
After asking the author, I'm closing this ticket:
< bartolin> hoelzro: I stumbled over an old ticket from you: RT #114228. Since
the failing code is not included and the links don't work anymore, the ticket
doesn't lead anywhere (IMHO). would you mind if I close the ticket?
< hoelzro> bartolin:
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #122716]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=122716 >
Oooh, I got a segfault!
https://gist.github.com/Nami-Doc/f0232a94cec52f0ec14c <- this
s
On Wed Nov 13 19:15:34 2013, coke wrote:
> On Mon Oct 08 13:45:22 2012, pawel.pab...@implix.com wrote:
> > rakudo: try { CATCH { ~$! }; die } # shortest form that
> > segfaults on my machine
> > rakudo 870d18: OUTPUT«(signal SEGV)»
> > rakudo: say $*PERL
> > rakudo 870d18: OUTPUT«("name" => "ra
On Mon Oct 08 13:45:22 2012, pawel.pab...@implix.com wrote:
> rakudo: try { CATCH { ~$! }; die } # shortest form that
> segfaults on my machine
> rakudo 870d18: OUTPUT«(signal SEGV)»
> rakudo: say $*PERL
> rakudo 870d18: OUTPUT«("name" => "rakudo", "compiler" =>
> {"name" => "rakudo", "ver" =>
On Mon Oct 15 04:19:04 2012, masak wrote:
> oh btw, I found this while you were away :)
> echo -e 'my \\a = any set <1 2 3>; \n say 1 ~~ a' | perl6
> Segmentation fault (core dumped)
> works fine if you omit the \n, though.
> has it been RT'd?
> I
x27;
/usr/local/bin/nom: line 3: 5894 Segmentation fault
/home/masak/ours/nom-rakudo/install/bin/perl6 "$@"
$ nom -e '.say for (1, 3, *x* ... 233)[1..3]'
3
111
333
(cue
a = any set <1 2 3>; \n say 1 ~~ a' | perl6
Segmentation fault (core dumped)
works fine if you omit the \n, though.
has it been RT'd?
I've been too busy trying to break rakudo to file bugs :P
* masak submits rakudobug
# New Ticket Created by Paweł Pabian
# Please include the string: [perl #115184]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org:443/rt3/Ticket/Display.html?id=115184 >
rakudo: try { CATCH { ~$! }; die } # shortest form that segfaults on my
machine
On Wed, Aug 29, 2012 at 11:24:24AM -0500, Patrick R. Michaud wrote:
> On Mon, Aug 27, 2012 at 12:16:08AM +0300, Gabor Szabo wrote:
> > After updating Rakudo to the latest and increasing the swap disk to 3
> > Gb I get this Segmentation fault.
> >
> > /home/gabor/work/
On Mon, Aug 27, 2012 at 12:16:08AM +0300, Gabor Szabo wrote:
> After updating Rakudo to the latest and increasing the swap disk to 3
> Gb I get this Segmentation fault.
>
> /home/gabor/work/rakudo_b/install/bin/parrot --library=src/stage0
> src/stage0/nqp.pbc \
> --t
After updating Rakudo to the latest and increasing the swap disk to 3
Gb I get this Segmentation fault.
Gabor
cd src/6model/reprs && cc -c -o CStr.o -I../../../src/pmc
-I/home/gabor/work/rakudo_b/install/include/parrot/4.4.0-devel
-I/home/gabor/work/rakudo_b/install/include/parrot/4.4
ge1/nqpmo.pbc] Segmentation fault (core dumped)
Command failed (status 512): make
Command failed (status 512): /usr/bin/perl Configure.pl
--with-parrot=/home/gabor/work/rakudo_b/install/bin/parrot
--make-install
This is an 64 bit Ubuntu 12.4 VPS (hosted on Linode) with 512 Mb
memory and 1 Gb swap sp
# New Ticket Created by Moritz Lenz
# Please include the string: [perl #113394]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org:443/rt3/Ticket/Display.html?id=113394 >
09:47 < moritz> p6: sub f { gather loop { take 1; return } }; say f
09:47 <+p6eval
# New Ticket Created by Moritz Lenz
# Please include the string: [perl #112906]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org:443/rt3/Ticket/Display.html?id=112906 >
< moritz> r: enum day (:Sun(1), 'Mon', 'Tue', 'Wed', 'Thu', 'Fri',
'Sat'); say day
On Mon Mar 23 13:09:56 2009, szab...@gmail.com wrote:
> I am not sure if this is a Parrot or Rakudo bug
> or just a plain invalid usage on my side.
>
> The following code runs, prints the prompt but when I
> enter a response I get a Segmentation fault.
>
> Gabor
>
&g
# New Ticket Created by Paweł Pabian
# Please include the string: [perl #101912]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org:443/rt3/Ticket/Display.html?id=101912 >
[19:58] everyone: can you please confirm segfault in this code on your
machines
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #99938]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org:443/rt3/Ticket/Display.html?id=99938 >
nom: state $blar;
nom 6fd077: OUTPUT«(signal SEGV)»
epic fel
:)
* masak submits
I
>> enter a response I get a Segmentation fault.
>>
>> Gabor
>>
>>
>> #!/usr/bin/perl
>> use strict;
>> use warnings;
>>
>>
>> # Needs two environment variables:
>> # PARROT_DIR needs to point to the directory where par
On Mon Mar 23 13:09:56 2009, szab...@gmail.com wrote:
> I am not sure if this is a Parrot or Rakudo bug
> or just a plain invalid usage on my side.
>
> The following code runs, prints the prompt but when I
> enter a response I get a Segmentation fault.
>
> Gabor
>
&g
Hi,
actually, I expected some sort of error, but no segaful
2009/8/30 fREW Schmidt via RT :
> What did you expect this to produce? Generally speaking I would have
> tried to do 1..$_, but maybe you are doing something different.
>
# New Ticket Created by Ilya Belikin
# Please include the string: [perl #68788]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68788 >
Hi there,
this code produce segmentation fault on the Rakudo bd51ce26:
sa
# New Ticket Created by "Kyle Hasselbacher"
# Please include the string: [perl #68554]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=68554 >
These segmentation fault:
perl6 -e 'try { 1/0 }; say $!.WHAT&
ide.
The following code runs, prints the prompt but when I
enter a response I get a Segmentation fault.
Gabor
#!/usr/bin/perl
use strict;
use warnings;
# Needs two environment variables:
# PARROT_DIR needs to point to the directory where parrot was checked out
# export LD_LIBRARY_PATH=$PARROT_
;matched' !! 'no match';
# Output:
in value()
in TOP()
Segmentation fault
in gdb:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f869d59c6f0 (LWP 10687)]
0x7f869cd7bcac in Parrot_pcc_invoke_from_sig_object (interp=Cannot
access memory at address 0x7ff
Thanks for the response.
I downloaded parrot onto my office machine (35397), and tested as you
suggested. All worked and in fact I couldnt reproduce the bug!!! :((
I will try again with parrot at home with version 35286
This happened to me before - I got a segmentation fault working with a
segmentation fault with the following program (also
attached).
I am using rakudo from parrot 35286
When I run the program below, it runs and I get almost the right
answer
(but uninitialised values and
incorrect output).
But when I comment out the 'say' line and uncomment the line below i
On Sat Jan 10 12:19:38 2009, richardh wrote:
> Getting a wierd segmentation fault with the following program (also
> attached).
>
> I am using rakudo from parrot 35286
>
> When I run the program below, it runs and I get almost the right
> answer
> (but uninitialised value
# New Ticket Created by Richard Hainsworth
# Please include the string: [perl #62176]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=62176 >
Getting a wierd segmentation fault with the following program (also
attac
On Sat Jan 10 12:19:38 2009, richardh wrote:
> Getting a wierd segmentation fault with the following program (also
> attached).
>
> I am using rakudo from parrot 35286
> [...]
Try running the script using parrot directly instead of the "perl6"
binary, and let us
James Keenan via RT wrote:
> On Thu Nov 13 13:57:34 2008, [EMAIL PROTECTED] wrote:
>> On Thursday 13 November 2008 13:54:36 James Keenan via RT wrote:
>>
>> > At r32625, I am observing this on Darwin/PPC -- but it passes on
>> > Linux/i386. Darwin below.
>>
>> Is the backtrace the same as the
On Thursday 13 November 2008 13:54:36 James Keenan via RT wrote:
> At r32625, I am observing this on Darwin/PPC -- but it passes on
> Linux/i386. Darwin below.
Is the backtrace the same as the one Moritz posted?
-- c
t t/pmc/pmc_3.pasm
All names ok.
Segmentation fault
With this backtrace:
(gdb) bt
#0 0xb7c07069 in Parrot_cx_delete_task (interp=0x8e6a048, task=0x8eddfac)
at src/scheduler.c:388
#1 0xb7d57e64 in Parrot_Timer_destroy (interp=0x8e6a048, pmc=0x8eddfac)
at ./src/pmc/timer.pmc:191
#2 0xb7bb7
On Tue Jul 29 00:38:29 2008, tuxdna wrote:
> I found that it is now working correctly in the latest revision 29838.
resolved
t seems that every program that starts with 'say' produces a
> Segmentation fault on my system
> * I will happily provide additional info (if requested) or test newer
> versions on my PC to verify that the bug is present/gone.
I just fixed one such bug in optimized builds (r300
icu-dev, libicu38 packages before configuration
* cd parrot-0.6.4; perl Configure.pl; make; cd languages/perl6; make perl6
* It seems that every program that starts with 'say' produces a
Segmentation fault on my system
* I will happily provide additional info (if requested) or test newer
v
erl6 -e 'exit'
$ ./perl6 -e 'sub a { exit }; a()'
But this doesn't:
$ ./perl6 -e 'sub a { b() }; sub b { exit }; a()'
perl6(26935) malloc: *** error for object 0x27c4c40: double free
*** set a breakpoint in malloc_error_break to debug
Segmentation fault
erl6/perl6 ./perl6
/usr/bin/perl -MExtUtils::Command -e ExtUtils::Command::chmod 0755 ./perl6
./perl6 -e"say 'Hello, world.'"
make: *** [perl6] Segmentation fault
make: *** Deleting file `perl6'
There was some vtable initialized wrongly with 0xdeadbeef value inside
src/exception
$ languages/perl6/perl6 -e'say "Hello"'
Segmentation fault
$ gdb languages/perl6/perl6
GNU gdb Red Hat Linux (6.6-35.fc8rh)
...
(gdb) run -e'say "Hello"'
Starting program: /home/saleem/work/compiler/parrot/languages/perl6/perl6
Program received signal
hello
>
[EMAIL PROTECTED] parrot]$ languages/perl6/perl6 -e 'say "hello"'
Segmentation fault
Hmm:
[EMAIL PROTECTED] parrot]$ languages/perl6/perl6 -e ' say "hello"'
hello
[EMAIL PROTECTED] parrot]$ languages/perl6/perl6 -e 'say "hello"'
/languages/perl6'
/usr/bin/perl -MExtUtils::Command -e cp languages/perl6/perl6 ./perl6
/usr/bin/perl -MExtUtils::Command -e ExtUtils::Command::chmod 0755 ./perl6
./perl6 -e"say 'Hello, world.'"
make: *** [perl6] Segmentation fault
make: *** Deleting file `perl6'
This als
Patrick R. Michaud via RT wrote:
> Is this still segfaulting in the current head?
No, seems fixed.
Moritz
--
Moritz Lenz
http://moritz.faui2k3.org/ | http://perl-6.de/
Is this still segfaulting in the current head?
Pm
Will Coleda via RT wrote:
> On Sun Jun 01 11:06:10 2008, [EMAIL PROTECTED] wrote:
>> Hi,
>>
>> parrot + perl6 as of r28017 segfault for me while running
>> t/spec/S29-array/push.rakudo.
>> Attached is a reduced test case that produces an assertion failure with
>> --runcore=gcdebug:
>>
>> $ ../../
On Sun Jun 01 11:06:10 2008, [EMAIL PROTECTED] wrote:
> Hi,
>
> parrot + perl6 as of r28017 segfault for me while running
> t/spec/S29-array/push.rakudo.
> Attached is a reduced test case that produces an assertion failure with
> --runcore=gcdebug:
>
> $ ../../parrot --runcore=gcdebug perl6.pbc p
# New Ticket Created by Moritz Lenz
# Please include the string: [perl #55164]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55164 >
Hi,
parrot + perl6 as of r28017 segfault for me while running
t/spec/S29-array/push.raku
Hi all,
A Segmentation fault occurs in the languages/lua/t/tables_3.pir.
This test is a simple table creation (with 1000 items) :
a = {}
for i=1,1000 do a[i] = i*2 end
print(a[9])
This problem started with revision 11586.
In the previous Lua PMC implementation (r11478
[EMAIL PROTECTED] (via RT) wrote:
Objective:
Parrot stops for segmentation fault when "-E (--pre-process-only)"
option is specified.
This patch fixes this bug.
Thanks, applied -r8914
(Please not that the preprocessor is currently not uptodate and doesn't
process all t
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #36852]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36852 >
Objective:
Parrot stops for segmentation fault when "-E (--pre-proc
Cory Spencer <[EMAIL PROTECTED]> wrote:
> The latest Parrot CVS checkout segfaults for me on the following code:
[ ... ]
> It appears that the "store_lex" opcode is to blame - when no lexical pad
> has been created and you attempt to store a lexical, the SEGV is
> generated.
Yep. Throws an exce
The latest Parrot CVS checkout segfaults for me on the following code:
.sub _main
.local pmc foo
foo = new Integer
foo = 3
# new_pad 0
store_lex "foo", foo
end
.end
It appears that the "store_lex" opcode is to blame - when no lexical pad
has been created and you att
Chris Allan <[EMAIL PROTECTED]> wrote:
> Hello,
> I've just started trying to experiment with parrot, and I keep getting
> segmentation faults, eg when running the following one-liner:
> set I0, 7
end
is missing. Program flow just continues with executing garbage.
> I also noticed what seems
[New Thread 16384 (LWP 16833)]
[New Thread 32769 (LWP 16834)]
[New Thread 16386 (LWP 16835)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 16833)]
0x0807f9ec in runops_slow_core (interpreter=0x823bc90, pc=0x827ed34)
at src/runops_cores.c:116
116
89 matches
Mail list logo
