Bug 958470 - [abrt] mysql-workbench-5.2.47-2.fc17: ValueRef: Process /usr/libexec/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] mysql-workbench-5.2.47-2.fc17: ValueRef: Process /usr/libexec/mysql-wo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql-workbench
Version: 17
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1f6b115a57ac2a601fc06983c0f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-01 15:14 UTC by Leon
Modified: 2013-08-01 00:24 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 00:24:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (118.71 KB, text/plain)
2013-05-01 15:14 UTC, Leon
no flags Details
File: cgroup (127 bytes, text/plain)
2013-05-01 15:14 UTC, Leon
no flags Details
File: core_backtrace (7.64 KB, text/plain)
2013-05-01 15:14 UTC, Leon
no flags Details
File: dso_list (15.14 KB, text/plain)
2013-05-01 15:14 UTC, Leon
no flags Details
File: environ (2.62 KB, text/plain)
2013-05-01 15:14 UTC, Leon
no flags Details
File: limits (1.29 KB, text/plain)
2013-05-01 15:14 UTC, Leon
no flags Details
File: maps (47.32 KB, text/plain)
2013-05-01 15:15 UTC, Leon
no flags Details
File: open_fds (391 bytes, text/plain)
2013-05-01 15:15 UTC, Leon
no flags Details
File: proc_pid_status (801 bytes, text/plain)
2013-05-01 15:15 UTC, Leon
no flags Details
File: smolt_data (2.58 KB, text/plain)
2013-05-01 15:15 UTC, Leon
no flags Details
File: xsession_errors (13.68 KB, text/plain)
2013-05-01 15:15 UTC, Leon
no flags Details

Description Leon 2013-05-01 15:14:02 UTC
Description of problem:
1) Selected Manage Connections
2) Selected a database
3) Selected "Duplicate" option
Crash


Version-Release number of selected component:
mysql-workbench-5.2.47-2.fc17

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/mysql-workbench-bin
crash_function: ValueRef
executable:     /usr/libexec/mysql-workbench-bin
kernel:         3.8.4-102.fc17.i686
uid:            1000
ureports_counter: 1
var_log_messages: May  1 17:01:50 localhost abrt[8818]: Saved core dump of pid 7513 (/usr/libexec/mysql-workbench-bin) to /var/spool/abrt/ccpp-2013-05-01-17:01:48-7513 (91951104 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ValueRef at ../../library/grt/src/grtpp.h:216
 #1 BaseListRef at ../../library/grt/src/grtpp.h:1011
 #2 ListRef at ../../library/grt/src/grtpp.h:1167
 #3 drivers at ../../generated/grts/structs.db.mgmt.h:1334
 #4 grtui::DbConnectPanel::selected_driver at grtui/grtdb_connect_panel.cpp:447
 #5 grtui::DbConnectionEditor::add_stored_conn at grtui/grtdb_connection_editor.cpp:233
 #6 boost::_mfi::mf1<void, grtui::DbConnectionEditor, bool>::operator() at /usr/include/boost/bind/mem_fn_template.hpp:165
 #7 operator()<boost::_mfi::mf1<void, grtui::DbConnectionEditor, bool>, boost::_bi::list0> at /usr/include/boost/bind/bind.hpp:313
 #8 operator() at /usr/include/boost/bind/bind_template.hpp:20
 #9 boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf1<void, grtui::DbConnectionEditor, bool>, boost::_bi::list2<boost::_bi::value<grtui::DbConnectionEditor*>, boost::_bi::value<bool> > >, void>::invoke at /usr/include/boost/function/function_template.hpp:153

Comment 1 Leon 2013-05-01 15:14:13 UTC
Created attachment 742240 [details]
File: backtrace

Comment 2 Leon 2013-05-01 15:14:36 UTC
Created attachment 742241 [details]
File: cgroup

Comment 3 Leon 2013-05-01 15:14:42 UTC
Created attachment 742242 [details]
File: core_backtrace

Comment 4 Leon 2013-05-01 15:14:45 UTC
Created attachment 742243 [details]
File: dso_list

Comment 5 Leon 2013-05-01 15:14:49 UTC
Created attachment 742244 [details]
File: environ

Comment 6 Leon 2013-05-01 15:14:53 UTC
Created attachment 742245 [details]
File: limits

Comment 7 Leon 2013-05-01 15:15:01 UTC
Created attachment 742246 [details]
File: maps

Comment 8 Leon 2013-05-01 15:15:08 UTC
Created attachment 742247 [details]
File: open_fds

Comment 9 Leon 2013-05-01 15:15:11 UTC
Created attachment 742248 [details]
File: proc_pid_status

Comment 10 Leon 2013-05-01 15:15:15 UTC
Created attachment 742249 [details]
File: smolt_data

Comment 11 Leon 2013-05-01 15:15:21 UTC
Created attachment 742250 [details]
File: xsession_errors

Comment 12 Fedora End Of Life 2013-07-03 22:28:18 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 13 Fedora End Of Life 2013-08-01 00:24:40 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.


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