Hide Forgot
Description of problem: This is current, updated F19 running SELinux enforced. Eclipse was hanging when creating new class, so I started poking around with strace and ltrace, and noticed this. The SEGV do not show up when not running ltrace, so it's possible that it's really a Heisenbug due to ltrace. Version-Release number of selected component (if applicable): eclipse-platform-4.3.1-5.fc19.x86_64 How reproducible: happens every time Steps to Reproduce: 1. ltrace -f eclipse Actual results: .... [pid 27068] --- Called exec() --- [pid 27068] __libc_start_main(0x400620, 54, 0x7fff92297be8, 0x400780 <unfinished ...> [pid 27068] JLI_Launch(54, 0x7fff92297be8, 1, 0CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith CompilerOracle: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.<init> CompilerOracle: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate CompilerOracle: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding CompilerOracle: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile CompilerOracle: exclude org/eclipse/tycho/core/osgitools/EquinoxResolver.newState <no return ...> [pid 27093] +++ exited (status 0) +++ [pid 27090] +++ exited (status 0) +++ [pid 27069] --- SIGSEGV (Segmentation fault) --- [pid 27096] +++ exited (status 0) +++ [pid 27069] --- SIGSEGV (Segmentation fault) --- ... more SEGV from 27069 ... [pid 27069] --- SIGSEGV (Segmentation fault) --- [pid 27100] +++ exited (status 0) +++ [pid 27069] --- SIGSEGV (Segmentation fault) --- [pid 27069] --- SIGSEGV (Segmentation fault) --- [pid 27069] --- SIGSEGV (Segmentation fault) --- [pid 27069] --- SIGSEGV (Segmentation fault) --- [pid 27102] --- SIGSEGV (Segmentation fault) --- ... Expected results: no SEGV errors Additional info:
I tried this and despite all the sigsegv on console eclipse started properly so I would say it's due to ltrace.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.