[Bug 598989] New: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by
signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=598989
Summary: [abrt] crash in perl-Padre-0.50-4.fc13: Process
/usr/bin/perl was killed by signal 11 (SIGSEGV)
Product: Fedora
Version: 13
Platform: x86_64
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:70e28391c1a250dd6698df00e84aff62011f8668
Severity: medium
Priority: low
Component: perl-Padre
AssignedTo: mmaslano(a)redhat.com
ReportedBy: rob+redhat(a)pangalactic.org
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com,
mmaslano(a)redhat.com, ppisar(a)redhat.com
Classification: Fedora
abrt 1.1.0 detected a crash.
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/perl /usr/bin/padre
comment: See "How to reproduce" for instructions. I verified this twice.
Problem does not occur when run locally.
component: perl-Padre
crash_function: _gdk_x11_screen_process_owner_change
executable: /usr/bin/perl
global_uuid: 70e28391c1a250dd6698df00e84aff62011f8668
kernel: 2.6.33.4-95.fc13.x86_64
package: perl-Padre-0.50-4.fc13
rating: 4
reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
-----
1. Start Hummingbird Exceed 12.0.0.124 on a Windows XP system
2. SSH into a Fedora 13 system with X11 tunnelling enabled using PuTTY
3. Start padre, loading a perl5 source file (e.g. "padre dbi-test.pl")
4. Select a module name such as "DBI" and press F2
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.