Bug 695044 - [abrt] mysql-workbench-5.2.33b-1.fc14: x86_fallback_frame_state: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] mysql-workbench-5.2.33b-1.fc14: x86_fallback_frame_state: Process /usr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql-workbench
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f0ccb4f937a6ed7527b3a717f57...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-10 03:42 UTC by Michael Kopinsky
Modified: 2011-06-10 14:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-10 14:20:17 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (46.45 KB, text/plain)
2011-04-10 03:42 UTC, Michael Kopinsky 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Michael Kopinsky 2011-04-10 03:42:14 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 47566 bytes
cmdline: /usr/bin/mysql-workbench-bin
comment: This has happened three times in a row (with the same table; haven't tried changing variables)
component: mysql-workbench
Attached file: coredump, 55578624 bytes
crash_function: x86_fallback_frame_state
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.35.11-83.fc14.i686
package: mysql-workbench-5.2.33b-1.fc14
rating: 4
reason: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302406830
uid: 500

How to reproduce
-----
1. Create EER model from an existing database
2. Create new table in MySQL workbench GUI
3. Right click on new table, click "Copy SQL to clipboard"
Comment 1 Michael Kopinsky 2011-04-10 03:42:18 UTC 
Created attachment 491031 [details]
File: backtrace
Comment 2 Remi Collet 2011-06-10 14:20:17 UTC 
Version 5.2.34 is now available in the update.
Note You need to log in before you can comment on or make changes to this bug.