Bug 658509

Summary: [abrt] mysql-workbench-5.2.30-1.fc14: adjust_pointer<void>: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: ricardo.gladwell
Component: mysql-workbenchAssignee: Remi Collet <fedora>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: fedora, pcsnow
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:66f4d8cc49c7047c64ce6ea80577ff88e6868316
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-09 16:09:44 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 Flags
File: backtrace none

Description ricardo.gladwell 2010-11-30 15:35:11 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/mysql-workbench-bin
component: mysql-workbench
crash_function: adjust_pointer<void>
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.35.6-48.fc14.i686.PAE
package: mysql-workbench-5.2.30-1.fc14
rating: 4
reason: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Just viewing tables in the editor mode.
time: 1291130654
uid: 500
Comment 1 ricardo.gladwell 2010-11-30 15:35:53 UTC 
Created attachment 463757 [details]
File: backtrace
Comment 2 ricardo.gladwell 2010-11-30 15:58:10 UTC 
Correction: deleting a table from the SQL editor view/mode.
Comment 3 Paul Campbell 2011-02-06 01:36:36 UTC 
Package: mysql-workbench-5.2.30-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. not sure
2.
3.


Comment
-----
deleteing a table
Comment 4 Remi Collet 2011-03-09 16:09:44 UTC 
I hope new version (which fixes a lot of bug) will fixes this one.

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