Bug 610336 - [abrt] crash in wxGlade-0.6.3tip20100625-1.fc13: GetStaticBoxBorders: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in wxGlade-0.6.3tip20100625-1.fc13: GetStaticBoxBorders: Process...
Keywords:
Status: CLOSED DUPLICATE of bug 608348
Alias: None
Product: Fedora
Classification: Fedora
Component: wxGlade
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Miao ZhiCheng
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:dc76dcce230821c83d6170436a4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-02 05:59 UTC by Bruce vaNorman
Modified: 2010-09-18 22:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-18 22:29:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (26.84 KB, text/plain)
2010-07-02 05:59 UTC, Bruce vaNorman 		no flags Details
View All

Description Bruce vaNorman 2010-07-02 05:59:14 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: python /usr/share/wxGlade/wxglade.py
comment: open, generate code, and exit has no problem, I'll test to see if "preview" frame without change causes the problem. FYI the change was to alter the frame width from 800 to 799. The generated code and the wxg appear undamaged. - Further testing: change not required, but frame preview is.
component: wxGlade
crash_function: GetStaticBoxBorders
executable: /usr/bin/python
global_uuid: dc76dcce230821c83d6170436a4e6ea35ed1c65d
kernel: 2.6.33.5-124.fc13.i686.PAE
package: wxGlade-0.6.3tip20100625-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.open old wxg
2.make change, save, generate code
3.exit
Comment 1 Bruce vaNorman 2010-07-02 05:59:16 UTC 
Created attachment 428619 [details]
File: backtrace
Comment 2 Miao ZhiCheng 2010-09-18 22:29:24 UTC 

*** This bug has been marked as a duplicate of bug 608348 ***
Note You need to log in before you can comment on or make changes to this bug.