Bug 95707 - Errors while debugging Eclipse application
Summary: Errors while debugging Eclipse application
Status: RESOLVED DUPLICATE of bug 94452
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-18 03:12 EDT by Sergey Prigogin CLA
Modified: 2005-05-18 08:56 EDT (History)
0 users

See Also:

Attachments
Log file fragment (24.74 KB, text/plain)
2005-05-18 03:14 EDT, Sergey Prigogin CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Prigogin CLA 2005-05-18 03:12:43 EDT 
When debugging Eclipse application I see periodic errors written to the log 
file (attached)
Comment 1 Sergey Prigogin CLA 2005-05-18 03:14:18 EDT 
Created attachment 21315 [details]
Log file fragment
Comment 2 Sergey Prigogin CLA 2005-05-18 03:27:49 EDT 
Other symptoms:
When I suspended the VM of the application being debugged, some threads 
including main did not show any stack frames:
org.eclipse.core.launcher.Main at localhost:1922 (Suspended)
	System Thread [Finalizer] (Suspended)
		Object.wait(long) line: not available [native method]
		ReferenceQueue.remove(long) line: not available
		ReferenceQueue.remove() line: not available
		Finalizer$FinalizerThread.run() line: not available
	System Thread [Reference Handler] (Suspended)
		Object.wait(long) line: not available [native method]
		Reference$Lock(Object).wait() line: not available
		Reference$ReferenceHandler.run() line: not available
	Thread [main] (Suspended)
	System Thread [Signal Dispatcher] (Suspended)
	Thread [Framework Event Dispatcher] (Suspended)
		Object.wait(long) line: not available [native method]
		EventThread(Object).wait() line: not available
		EventThread.getNextEvent() line: 162
		EventThread.run() line: 100
	Thread [Start Level Event Dispatcher] (Suspended)
		Object.wait(long) line: not available [native method]
		EventThread(Object).wait() line: not available
		EventThread.getNextEvent() line: 162
		EventThread.run() line: 100
	Thread [Worker-0] (Suspended)
		Object.wait(long) line: not available [native method]
		WorkerPool.sleep(long) line: 168
		WorkerPool.startJob(Worker) line: 200
		Worker.run() line: 60
	Thread [Java indexing] (Suspended)
		Object.wait(long) line: not available [native method]
		IndexManager(Object).wait() line: not available
		IndexManager(JobManager).run() line: 346
		Thread.run() line: not available
	Thread [Worker-1] (Suspended)
	Thread [Worker-2] (Suspended)
		Object.wait(long) line: not available [native method]
		ThreadJob.joinRun(IProgressMonitor) line: 170
		ImplicitJobs.begin(ISchedulingRule, IProgressMonitor, boolean) 
line: 88
		JobManager.beginRule(ISchedulingRule, IProgressMonitor) line: 
190
		StringPoolJob.run(IProgressMonitor) line: 91
		Worker.run() line: 67
	Thread [Worker-3] (Suspended)
	Thread [Worker-4] (Suspended)
	Thread [Worker-5] (Suspended)

After clicking few more times in Debug view main Eclipse hang with 100% CPU 
utilization for 3-5 minutes, but then recovered from that state.
Comment 3 Darin Wright CLA 2005-05-18 08:56:31 EDT 
The timeouts are a dup of bug 94452. The stack frame problem is likely a dup 
of bug 94530.

*** This bug has been marked as a duplicate of 94452 ***