Bug 626920
Summary: | [abrt] crash in perl-Padre-0.32-2.fc12: wxStyledTextCtrl::SendMsg: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Scott R. Godin <rhbugzilla> | ||||||||||
Component: | perl-Padre | Assignee: | Marcela Mašláňová <mmaslano> | ||||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | 12 | CC: | mmaslano, perl-devel | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | abrt_hash:5d7988fcae0c432f77545581c126f5d9ad6fd0fd | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2010-11-10 09:45:18 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Scott R. Godin
2010-08-24 17:18:16 UTC
Created an attachment (id=440704) File: backtrace Can you elaborate more what you did. I'm not experienced with Padre.
> basically working with the new module creation tool,
There is no such tool Plugins → Plugin Manager. Did you mean File → New → Perl 5 module?
I tried the New Perl 5 module, and to open or close some files but no crash occurred. (Actually I used x86_64 in virtual machine.)
Do you have an reliable procedure ho to invoke the crash?
According back trace the problem is in threads or WxWidgets or WxWidgets perl binding. OTOH, I noticed that padre requires newer Thread::Queue, because the current one does not support Thread::Queue->insert:
Can't locate object method "insert" via package "Thread::Queue" at /usr/lib/perl5/vendor_perl/5.10.0/Padre/TaskManager.pm line 358.
Perl exited with active threads:
1 running and unjoined
0 finished and unjoined
0 running and detached
Created attachment 440987 [details]
step one
step one after choosing initial file->new->Perl Distribution (Module::Starter)
Created attachment 440988 [details]
step two
step two, it asks me whether I want to open the module it apparently created
Created attachment 440989 [details] step three showing opened tabs and close-box used > Did you mean File → New → Perl 5 module? It was File -> New -> "Perl Distribution (Module::Starter)" I've taken a series of screenshots which I attached, the last of which (step three) has the red circle indicating the closebox I was clicking, which yes does retrigger the bug reliably Thread::Queue on my machine appears to be version 2.00 This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 Would you mind test it with new Padre? F-14 contains version 0.64. Update of Padre in older releases is quite hard, almost impossible. This bug can't be reproduced in Fedora-14 (v0.64). In F-13 is v0.50, so hopefully it's fixed in both these releases. Update into F-12 is not possible because Padre has a lot of dependencies. |