Bug 926915

Summary: [abrt] anjuta-3.6.2-1.fc18: book_tree_find_book: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanzaro>
Component: anjutaAssignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jhs, kalevlember, mclasen, rakesh.pandit
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f9fe4098d95f1c60cf41e382847f012eea8e9a8c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:14:51 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
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Michael Catanzaro 2013-03-24 02:41:32 UTC
Description of problem:
I was editing Vala code (gnome-chess!) in Anjuta. In a terminal (outside of Anjuta), I ran configure/make/make install. Sometime during this process, Anjuta crashed.

Version-Release number of selected component:
anjuta-3.6.2-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        anjuta
crash_function: book_tree_find_book
executable:     /usr/bin/anjuta
kernel:         3.8.3-203.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 book_tree_find_book at dh-book-tree.c:266
 #1 book_tree_add_book_to_store at dh-book-tree.c:408
 #6 book_manager_new_possible_book_cb at dh-book-manager.c:371
 #11 g_main_context_iteration at gmain.c:3351
 #12 g_application_run at gapplication.c:1624

Comment 1 Michael Catanzaro 2013-03-24 02:41:34 UTC
Created attachment 715381 [details]
File: backtrace

Comment 2 Michael Catanzaro 2013-03-24 02:41:36 UTC
Created attachment 715382 [details]
File: build_ids

Comment 3 Michael Catanzaro 2013-03-24 02:41:38 UTC
Created attachment 715383 [details]
File: cgroup

Comment 4 Michael Catanzaro 2013-03-24 02:41:39 UTC
Created attachment 715384 [details]
File: core_backtrace

Comment 5 Michael Catanzaro 2013-03-24 02:41:40 UTC
Created attachment 715385 [details]
File: dso_list

Comment 6 Michael Catanzaro 2013-03-24 02:41:42 UTC
Created attachment 715386 [details]
File: environ

Comment 7 Michael Catanzaro 2013-03-24 02:41:44 UTC
Created attachment 715387 [details]
File: limits

Comment 8 Michael Catanzaro 2013-03-24 02:41:45 UTC
Created attachment 715388 [details]
File: maps

Comment 9 Michael Catanzaro 2013-03-24 02:41:47 UTC
Created attachment 715389 [details]
File: open_fds

Comment 10 Michael Catanzaro 2013-03-24 02:41:48 UTC
Created attachment 715390 [details]
File: proc_pid_status

Comment 11 Michael Catanzaro 2013-03-24 02:41:50 UTC
Created attachment 715391 [details]
File: var_log_messages

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

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 14 Fedora End Of Life 2014-02-05 20:14:51 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.