Bug 607739 - [abrt] crash in wxGlade-0.6.3tip20091130-2.fc13: GetStaticBoxBorders: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in wxGlade-0.6.3tip20091130-2.fc13: GetStaticBoxBorders: Process...
Status: CLOSED DUPLICATE of bug 603983
Alias: None
Product: Fedora
Classification: Fedora
Component: wxGlade   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Miao ZhiCheng
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:735a24bb4a910d8d466da4b50e3...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-24 17:11 UTC by Bruce vaNorman
Modified: 2010-06-25 01:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-25 01:41:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (26.75 KB, text/plain)
2010-06-24 17:11 UTC, Bruce vaNorman
no flags Details
File: comment (12.40 KB, text/plain)
2010-06-24 17:11 UTC, Bruce vaNorman
no flags Details

Description Bruce vaNorman 2010-06-24 17:11:49 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: python /usr/share/wxGlade/wxglade.py
Attached file: comment
component: wxGlade
crash_function: GetStaticBoxBorders
executable: /usr/bin/python
global_uuid: 735a24bb4a910d8d466da4b50e33d9fa258ffc9c
package: wxGlade-0.6.3tip20091130-2.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1.open up my wxg file
2.select "generate code"

Comment 1 Bruce vaNorman 2010-06-24 17:11:52 UTC
Created attachment 426654 [details]
File: backtrace

Comment 2 Bruce vaNorman 2010-06-24 17:11:54 UTC
Created attachment 426655 [details]
File: comment

Comment 3 Miao ZhiCheng 2010-06-25 01:41:19 UTC

*** This bug has been marked as a duplicate of bug 603983 ***

Note You need to log in before you can comment on or make changes to this bug.