Bug 1038830

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: