Description of problem:
I tried opening my workspace with a new version of eclipse. Eclipse asked me to update some components including pydev. I klicked yes and a couple of minutes later received a message that something crashed.
Eclipse seems to work fine though. Maybe no bug at all, but rather a wrong report?
Version-Release number of selected component:
cmdline: /usr/bin/python -u /usr/lib64/eclipse/dropins/pydev-core/eclipse/plugins/org.python.pydev_184.108.40.206510221100/pysrc/pycompletionserver.py 39600
runlevel: N 5
Thread no. 1 (10 frames)
#0 init_libpycomps at /usr/src/debug/libcomps-d86995b748419bf6ca36f1c7f233727736d2efd5/libcomps/src/python/src/pycomps.c:1110
#1 _PyImport_LoadDynamicModule at /usr/src/debug/Python-2.7.10/Python/importdl.c:53
#2 load_module at /usr/src/debug/Python-2.7.10/Python/import.c:1919
#3 import_submodule at /usr/src/debug/Python-2.7.10/Python/import.c:2704
#4 load_next at /usr/src/debug/Python-2.7.10/Python/import.c:2519
#5 import_module_level at /usr/src/debug/Python-2.7.10/Python/import.c:2228
#6 PyImport_ImportModuleLevel at /usr/src/debug/Python-2.7.10/Python/import.c:2292
#7 builtin___import__ at /usr/src/debug/Python-2.7.10/Python/bltinmodule.c:49
#8 PyObject_Call at /usr/src/debug/Python-2.7.10/Objects/abstract.c:2529
#9 PyEval_CallObjectWithKeywords at /usr/src/debug/Python-2.7.10/Python/ceval.c:3981
Potential duplicate: bug 1107994
Created attachment 1102431 [details]
Created attachment 1102432 [details]
Created attachment 1102433 [details]
Created attachment 1102434 [details]
Created attachment 1102435 [details]
Created attachment 1102436 [details]
Created attachment 1102437 [details]
Created attachment 1102438 [details]
Created attachment 1102439 [details]
Created attachment 1102440 [details]
Created attachment 1102441 [details]
Created attachment 1102442 [details]
Can you give us instructions how to reproduce this bug? If you still experience it yourself of course.
No, I have not succeeded reproducing it. I tried copying an old version of my workspace to my testing machine, but there it won't crash. I also had some physical hard drive related issues on the machine where the crash occurred, so maybe it was due to that.
In short: bug has not bothered me since, so maybe just close it.
*** This bug has been marked as a duplicate of bug 1244972 ***