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
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
20 matches
Mail list logo
