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=603502
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:1c0f880ad9686d02efbd3096ee944822c284105a Severity: medium Priority: low Component: perl-Padre AssignedTo: mmaslano@redhat.com ReportedBy: it_rom@gmx.de QAContact: extras-qa@fedoraproject.org CC: fedora-perl-devel-list@redhat.com, mmaslano@redhat.com, ppisar@redhat.com, psabata@redhat.com Classification: Fedora
abrt 1.1.1 detected a crash.
architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/perl /usr/bin/padre component: perl-Padre executable: /usr/bin/perl global_uuid: 1c0f880ad9686d02efbd3096ee944822c284105a kernel: 2.6.33.5-112.fc13.x86_64 package: perl-Padre-0.50-4.fc13 rating: 3 reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
How to reproduce ----- 1.closed padre through the gnome-terminal 2. 3.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=603502
--- Comment #1 from it_rom@gmx.de 2010-06-13 11:05:22 EDT --- Created an attachment (id=423642) --> (https://bugzilla.redhat.com/attachment.cgi?id=423642) File: backtrace
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=603502
Petr Pisar ppisar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|perl-Padre |wxGTK CC| |dan@danny.cz AssignedTo|mmaslano@redhat.com |dan@danny.cz
--- Comment #2 from Petr Pisar ppisar@redhat.com 2010-06-14 03:50:19 EDT --- It crashed somewhere in wxGTK package. Last stack frame is really strange. The cs:ip address points to unmapped page. Seems like a corruption of program counter. This is code of last known function:
// Is this object a kind of (a subclass of) 'info'? // E.g. is wxWindow a kind of wxObject? // Go from this class to superclass, taking into account // two possible base classes. bool wxObject::IsKindOf(wxClassInfo *info) const { wxClassInfo *thisInfo = GetClassInfo(); return (thisInfo) ? thisInfo->IsKindOf(info) : false ; }
According backtrace this function called another unknown one residing on invalid address. I guess some virtual method had invalid address in class method table.
Reassigning to wxGTK component.
I wasn't able to reproduce this bug.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=603502
--- Comment #3 from Bug Zapper triage@lists.fedoraproject.org 2011-06-02 07:02:55 EDT ---
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=603502
Bug Zapper triage@lists.fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX Flag|needinfo?(it_rom@gmx.de) | Last Closed| |2011-06-27 14:07:49
--- Comment #4 from Bug Zapper triage@lists.fedoraproject.org 2011-06-27 14:07:49 EDT ---
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
perl-devel@lists.fedoraproject.org