abrt 1.0.0 detected a crash. How to reproduce ----- 1.Start Anjuta with a project to load 2.Close the project once everything is loaded 3.Click on New to start a new project Comment: After closing the project automatically loaded at startup (because it was the last opened project and I have the open-the-last-project-at-startup option on) I clicked on New to start a new one and it crashed Attached file: backtrace cmdline: anjuta component: anjuta executable: /usr/bin/anjuta kernel: 2.6.31.6-166.fc12.x86_64 package: anjuta-1:2.28.1.0-2.fc12 rating: 4 reason: Process was terminated by signal 6
Created attachment 377961 [details] File: backtrace
Assertion failure in pa_tls_set(). Most likely caused by Thread Local Storage corruption due to anjuta's misuse of libxml2. Let's see: $ grep -r xmlCleanup * plugins/document-manager/anjuta-bookmarks.c: xmlCleanupParser(); plugins/language-manager/plugin.c: xmlCleanupParser(); These are suspicious. Debarshi / other developers, please see Lennart's "Heads-Up: Beware of xmlCleanupParser() when your package links against libxml2": http://lists.fedoraproject.org/pipermail/devel/2010-January/129117.html or read about how a similar bug was found in abiword: https://bugzilla.redhat.com/show_bug.cgi?id=532307#c111
*** Bug 553435 has been marked as a duplicate of this bug. ***
*** Bug 570915 has been marked as a duplicate of this bug. ***
How to reproduce ----- 1. Try to open or create new file 2. 3. Comment ----- As I was attempting to open an existing file, anjuta crashed. I also attempted to create a new file, same thing happens.
*** Bug 585677 has been marked as a duplicate of this bug. ***
*** Bug 598500 has been marked as a duplicate of this bug. ***
*** Bug 598503 has been marked as a duplicate of this bug. ***
*** Bug 603349 has been marked as a duplicate of this bug. ***
*** Bug 607749 has been marked as a duplicate of this bug. ***
Created attachment 426909 [details] never call xmlCleanupParser() This should fix it.
Given we have patch, I would guess this has been triaged.
*** Bug 617903 has been marked as a duplicate of this bug. ***
*** Bug 621770 has been marked as a duplicate of this bug. ***
*** Bug 618058 has been marked as a duplicate of this bug. ***
*** Bug 633119 has been marked as a duplicate of this bug. ***
*** Bug 623599 has been marked as a duplicate of this bug. ***
*** Bug 621622 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.