Bug 693201

Summary: [abrt] rakudo-star-0.0.2011.01_3.0.0-1.fc14: do_sub_pragmas: Process /usr/bin/perl6 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Richard A. Hogaboom <richard.hogaboom>
Component: rakudo-starAssignee: Gerd Pokorra <gp>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gp
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f2ae59b3d9302de2818b84cd7bc924fd84ac8f5a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-14 19:31:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Richard A. Hogaboom 2011-04-03 14:04:48 UTC 
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.
Comment 1 Richard A. Hogaboom 2011-04-03 14:04:50 UTC 
Created attachment 489655 [details]
File: backtrace
Comment 2 Gerd Pokorra 2011-04-13 11:32:12 UTC 
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
Comment 3 Richard A. Hogaboom 2011-04-13 17:34:46 UTC 
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?
Comment 4 Richard A. Hogaboom 2011-04-13 17:37:31 UTC 
Now, when I run "perl6" it gives just the > prompt.  However, I've got many updates recently.
Comment 5 Gerd Pokorra 2011-04-14 14:51:04 UTC 
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?
Comment 6 Richard A. Hogaboom 2011-04-14 15:19:35 UTC 
Close it.  I have no way of knowing which rpm solved it.  Thanx.