Bug 814235
Summary: | [abrt] cmake-gui-2.8.4-1.fc15: __GI_exit: Process /usr/bin/cmake-gui was killed by signal 11 (SIGSEGV) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | abeforu | ||||
Component: | cmake | Assignee: | Orion Poplawski <orion> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 15 | CC: | jakub, jreznik, law, orion, pertusus, pmachata, rdieter, schwab | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Unspecified | ||||||
URL: | http://public.kitware.com/Bug/view.php?id=13156 | ||||||
Whiteboard: | abrt_hash:a691137d913dffc44b1816df132df3ee5f09894b | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-08-07 20:00:40 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
abeforu
2012-04-19 12:39:36 UTC
Created attachment 578634 [details]
File: maps
Package: cmake-gui-2.8.4-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- not so sure. But I was working on CMAKE I did lock my screen for an hour or so and then came back to work. then the error occurred. Re-assigning to glibc for input since it appears to be happening in the guts of exit handling and I have no idea how to see what in the cmake/Qt code might be triggering this if anything. I'm pretty sure this is a race condition; getenv/setenv are not multi-thread safe and their use (directly or indirectly) in multi-threaded applications has caused numerous reports of this nature. We already know this is a application with 2 threads. One of them is inside getenv, but someone with more knowledge of the other libraries in use would need to audit them for uses of setenv/unsetenv. Obviously the other thread may have called setenv and returned so it's not showing up in the stack trace. Reassigning back to cmake for now... You can find good context on this issue: https://bugzilla.gnome.org/show_bug.cgi?id=659326 A google serach for __GI_getenv will show up numerous bugs which all appear to be distinct instances of this problem. Jeff - The one thing that seemed confusing to me was that the genenv call was from __GI_exit/__run_exit_handlers. Does that get called during normal operation? I made the assumption that is was during application exit. Reporter - Did the crash occur on exit of cmake-gui, or where you performing an operation? It seems to be on the exit path, which is unfortunate as it means that there's an inherent race in any multi-threaded application where one thread might be exiting while another is inside putenv/clearenv. I don't see a way to know why one thread from cmake-gui was on the exit path from the data in this BZ; it might be a normal part of its operation. It'd also be good to comfirm that cmake-gui has a path where it is calling putenv/clearenv. Based on the backtrace and the striking similarities to other reports I'm pretty sure it's the same core issue, but obviously we won't know for sure until we can confirm there's a way to have one thread exiting while another is in putenv/clearenv within cmake-gui. Just wandering the cmake sources shows a fair amount of mucking around with the environment. That's considered fundamentally unsafe in a multi-threaded application. Any changes to the environment need to occur before any threads are created. Filed upstream Package: cmake-gui-2.8.4-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- after closing CMAKE This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 |