Bug 598989
| Summary: | [abrt] crash in perl-Padre-0.50-4.fc13: Process /usr/bin/perl was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rob Riggs <rob+redhat> | ||||
| Component: | gtk2 | Assignee: | Matthias Clasen <mclasen> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | mclasen, mmaslano, perl-devel, pertusus, ppisar, rdieter | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| URL: | https://bugzilla.gnome.org/show_bug.cgi?id=609126 | ||||||
| Whiteboard: | abrt_hash:70e28391c1a250dd6698df00e84aff62011f8668 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-27 17:20:29 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
Rob Riggs
2010-06-02 13:46:01 UTC
Created attachment 419037 [details]
File: backtrace
Cannot reproduce on Linux to Linux (Xorg, putty or openssh for Linux, Fedora 13). Can you trigger the segfault always or is it random? Does it occur only when pressing F2 to open new window with help for given module or can you crash Padre with opening any other window? It looks more like gtk2 bug with interaction to Hummingbird Exceed X11 server. It segfaulted here: 0x0000003deb46b954 <+36>: callq 0x3deb41c658 <g_type_check_instance_cast@plt> => 0x0000003deb46b959 <+41>: mov 0x440(%rax),%rsi That means the gtk2 library tried to dereference return code of g_type_check_instance_cast@plt function at offset 0x440. And because rax was zero, the effective read address was 0x440. According memory mapping list, zeroth page was unmapped. Thus it's simple NULL pointer dereference in libgtk2++. I will check _gdk_x11_screen_process_owner_change() code in gdkscreen-x11.c later. This bug is tracked by upstream probably already: https://bugzilla.gnome.org/show_bug.cgi?id=609126 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 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. |