Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 17933 bytes cmdline: perl6 component: rakudo-star Attached file: coredump, 64995328 bytes crash_function: do_sub_pragmas executable: /usr/bin/perl6 kernel: 2.6.35.11-83.fc14.x86_64 package: rakudo-star-0.0.2011.01_3.0.0-1.fc14 rating: 4 reason: Process /usr/bin/perl6 was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1301839376 uid: 500 How to reproduce ----- 1. I just executed "perl6" on the command line with no arguments. 2. 3.
Created attachment 489655 [details] File: backtrace
Does this command parrot /usr/lib64/parrot/3.0.0/languages/perl6/perl6.pbc also crash? What do you have from this rpms installed? parrot-tools, parrot-devel, readline, readline-devel, libicu, libicu-devel Gerd
The "parrot /usr/lib64/parrot/3.0.0/languages/perl6/perl6.pbc" does not crash. It returns to a > prompt. parrot.x86_64 3.0.0-1.fc14 @updates parrot.i686 3.0.0-1.fc14 updates parrot-devel.i686 3.0.0-1.fc14 updates parrot-devel.x86_64 3.0.0-1.fc14 updates parrot-docs.noarch 3.0.0-1.fc14 updates parrot-tools.x86_64 3.0.0-1.fc14 updates readline.i386 6.1-2.fc14 fedora readline-devel.i386 6.1-2.fc14 fedora readline-static.x86_64 6.1-2.fc14 fedora libicu.x86_64 4.4.1-6.fc14 @updates libicu.i686 4.4.1-6.fc14 updates libicu-devel.i686 4.4.1-6.fc14 updates libicu-devel.x86_64 4.4.1-6.fc14 updates libicu-doc.noarch 4.4.1-6.fc14 updates There are other lines from "yum list" with parrot/readline/libicu in them, but not at the beginning. Can I email you the full "yum list" output? What email?
Now, when I run "perl6" it gives just the > prompt. However, I've got many updates recently.
You can sent me email to the address that you see when you logged-in in bugzilla and click on my name. It would be nice to know for me, which of the rpm solved the problem. So I would know which must be added as a "Require" in the rakudo-star spec file. But I afraid you will not be able to say what package of the list solve the problem. Can the ticket be closed?
Close it. I have no way of knowing which rpm solved it. Thanx.