Bug 870605 - [abrt] anjuta-3.4.4-1.fc17: g_str_hash: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Summary: [abrt] anjuta-3.4.4-1.fc17: g_str_hash: Process /usr/bin/anjuta was killed by...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anjuta
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:38f440815ab55e89e2c08715351...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-27 08:24 UTC by spsch1980
Modified: 2013-08-01 04:28 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 04:28:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: core_backtrace (1.97 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: environ (1.44 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: limits (1.29 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: backtrace (42.44 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: cgroup (129 bytes, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: smolt_data (5.26 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: xsession_errors (1.11 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: maps (51.55 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: dso_list (10.71 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: proc_pid_status (919 bytes, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: open_fds (1.22 KB, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details
File: var_log_messages (909 bytes, text/plain)
2012-10-27 08:24 UTC, spsch1980
no flags Details

Description spsch1980 2012-10-27 08:24:33 UTC
Description of problem:
Tried to add QT Libarys to a project via Menu Project, add libaries. 

Added all the libarys of QT.

From now on Anjuta keeps crashing and does not start again. 


Version-Release number of selected component:
anjuta-3.4.4-1.fc17

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
backtrace_rating: 4
cmdline:        anjuta
crash_function: g_str_hash
kernel:         3.6.2-4.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 g_str_hash at ghash.c:1730
: #1 g_hash_table_lookup_node at ghash.c:401
: #2 g_hash_table_lookup_extended at ghash.c:1110
: #3 sdb_engine_cache_lookup at symbol-db-engine-core.c:202
: #4 sdb_engine_add_new_language at symbol-db-engine-core.c:3146
: #5 sdb_engine_add_new_db_file at symbol-db-engine-core.c:3255
: #6 symbol_db_engine_add_new_files_full_async at symbol-db-engine-core.c:3534
: #7 symbol_db_engine_add_new_files_async at symbol-db-engine-core.c:3444
: #8 isymbol_manager_add_package at plugin.c:2632
: #12 g_signal_emit_by_name at gsignal.c:3393

Comment 1 spsch1980 2012-10-27 08:24:37 UTC
Created attachment 634132 [details]
File: core_backtrace

Comment 2 spsch1980 2012-10-27 08:24:39 UTC
Created attachment 634133 [details]
File: environ

Comment 3 spsch1980 2012-10-27 08:24:40 UTC
Created attachment 634134 [details]
File: limits

Comment 4 spsch1980 2012-10-27 08:24:43 UTC
Created attachment 634135 [details]
File: backtrace

Comment 5 spsch1980 2012-10-27 08:24:45 UTC
Created attachment 634136 [details]
File: cgroup

Comment 6 spsch1980 2012-10-27 08:24:47 UTC
Created attachment 634137 [details]
File: smolt_data

Comment 7 spsch1980 2012-10-27 08:24:49 UTC
Created attachment 634138 [details]
File: xsession_errors

Comment 8 spsch1980 2012-10-27 08:24:51 UTC
Created attachment 634139 [details]
File: maps

Comment 9 spsch1980 2012-10-27 08:24:53 UTC
Created attachment 634140 [details]
File: dso_list

Comment 10 spsch1980 2012-10-27 08:24:55 UTC
Created attachment 634141 [details]
File: proc_pid_status

Comment 11 spsch1980 2012-10-27 08:24:56 UTC
Created attachment 634142 [details]
File: open_fds

Comment 12 spsch1980 2012-10-27 08:24:58 UTC
Created attachment 634143 [details]
File: var_log_messages

Comment 13 Johannes Schmid 2012-10-28 12:35:00 UTC
I will try to reproduce this once I have time but for now you should be able to avoid the crash if you delete the files ~/.cache/anjuta/anjuta_sym_db.db and <project-path>/.anjuta_sym_db.db

Comment 14 spsch1980 2012-11-01 15:58:53 UTC
thx, tried that out, but did not work !

Comment 16 Fedora End Of Life 2013-07-04 00:35:47 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 17 Fedora End Of Life 2013-08-01 04:28:20 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.