Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348373

Summary:	Job found still running after platform shutdown.
Product:	[Tools] CDT	Reporter:	Jens Seidel <jensseidel>
Component:	cdt-debug	Assignee:	cdt-debug-inbox <cdt-debug-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	minor
Priority:	P3	CC:	cdtdoug, malaperle, marc.khouzam, pawel.1.piech
Version:	8.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Jens Seidel

2011-06-06 05:39:21 EDT

Build Identifier: 20110526-1053

My gdb failed to start because one of it's libraries it was linked against was not found. CDT did not properly recognize it. It tries to launch the debugger for ever (according to Progess Dialog) whereas the gdb console contains:

<terminated> myProgram Debug [C/C++ Application] gdb

Because of this I restarted the debugger via UI multiple times :-)

gdb Traces console contains

953,319 1-environment-cd /mylocaldir

A few times I found now the following stacktrace in the error log, probable one entry for each attempt to start gdb:

eclipse.buildId=I20110519-1138
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.linuxtools.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.linuxtools.product

Warning
Fri Jun 03 16:53:42 CEST 2011
Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.debug.internal.ui.DebugUIPlugin$8


Reproducible: Always

Comment 1 Jens Seidel

2011-06-06 05:54:08 EDT

This was the gdb error in the past:

$ gdb
gdb: error while loading shared libraries: libpython2.6.so.1.0: cannot open shared object file: No such file or directory

In this situation there is no possibility to cancel the CDT debugging process in the progress dialog (doesn't vanish from the dialog) and it also doesn't stop from alone (was in this state for more than 2 days :-)).

Comment 2 Marc Khouzam

2011-06-07 09:25:44 EDT

How did you build your gdb?  Maybe it can help us know how to reproduce this.

Comment 3 Jens Seidel

2011-06-11 14:55:31 EDT

(In reply to comment #2)
> How did you build your gdb?  Maybe it can help us know how to reproduce this.

Sorry, haven't seen this reply yet

I use Gentoo, a system which compiles all it's software itself and the problem happens after an upgrade of Python. Sometimes there is manual work required to get the software working again and it seems this was the case (and I didn't noticed it early enough). A call to revdep-rebuild or python-updater was missing :-))