Bug 174804 - 3.2.2: Debugger hangs on Mac OS X
Summary: 3.2.2: Debugger hangs on Mac OS X
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.2.2   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: readme
: 188772 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-20 11:44 EST by Uwe Schoeneberg CLA
Modified: 2007-05-23 16:59 EDT (History)
1 user (show)

See Also:

Attachments
updated eclipse.ini file (260 bytes, text/plain)
2007-02-23 11:30 EST, Darin Wright 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 Uwe Schoeneberg CLA 2007-02-20 11:44:00 EST 
Build ID: M20070212-1330 
// had to be reported under 3.2.1, 
// because bug reporter Version list did NOT provide 3.2.2

Steps To Reproduce:
1. create any Class with a main Method
2. set breakpoint in Method
3. start Debug As...
4. You'll have to switch manually to Debug View
5. Thread starts and hangs


More information:
Code works fine in following combinations:

3.2.2. on Windows XP
3.2.1. on Mac OS X
Comment 1 Darin Wright CLA 2007-02-20 12:33:56 EST 
Unable to reproduce on MacOS using 3.2.2 and 1.5 VM. What VM are you using?
Comment 2 Uwe Schoeneberg CLA 2007-02-23 05:34:40 EST 
(In reply to comment #1)
> Unable to reproduce on MacOS using 3.2.2 and 1.5 VM. What VM are you using?
> 

The problem is reproducible, but just under VM 1.4.2. Generating the following message on the operating system console:

java.lang.NoSuchMethodError: com.sun.jdi.VirtualMachineManager.createVirtualMachine(Lcom/sun/jdi/connect/spi/Connection;)Lcom/sun/jdi/VirtualMachine;
   at org.eclipse.jdi.internal.connect.ConnectorImpl.establishedConnection(ConnectorImpl.java:98)
   at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:129)
   at org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:78)
   at java.lang.Thread.run(Thread.java:552)

When launching Eclipse 3.2.2 under VM 1.5.0, there is no problem.

However, having re-read the release notes at http://www.eclipse.org/eclipse/development/readme_eclipse_3.2.2.html, these release notes claim: Apple Mac OS X: Version 3.2.2 has been tested against Java 2 Platform Standard Edition (J2SE) 1.4.2 service release 2 for Tiger.
Comment 3 Darin Wright CLA 2007-02-23 09:02:25 EST 
This smells like bug 118517. The eclipse.ini points to the wrong jdi.jar
Comment 4 Darin Wright CLA 2007-02-23 09:20:48 EST 
There is a manual workaround...

Edit the "eclipse.ini" file's -Xbootclasspath entry to point to the correct jar:

    org.eclipse.jdt.debug_3.2.2.r322_v20070130

The incorrect entry is (note the 3.2.1 vs 3.2.2)

    org.eclipse.jdt.debug_3.2.1.r322_v20070130
Comment 5 Darin Wright CLA 2007-02-23 11:30:04 EST 
Created attachment 59671 [details]
updated eclipse.ini file
Comment 6 Darin Wright CLA 2007-02-23 11:32:20 EST 
The eclipse.ini file is found by selecting the "Eclipse" executable, "Show Package Contents", and navigating into the "Contents/MacOS" folder.
Comment 7 Darin Wright CLA 2007-02-23 11:34:51 EST 
In Mac-speak: "inside the application bundle in the Eclipse.app/Contents/MacOS directory"
Comment 8 Darin Wright CLA 2007-02-23 11:39:50 EST 
Since 3.2.2 is released and there is manual workaround, we do not intend to re-build 3.2.2. The README notes for 3.2.2 will be updated. If another 3.2.x maintenance release is scheduled, we will update eclipse.ini for MacOS.
Comment 9 Darin Wright CLA 2007-05-23 16:59:41 EDT 
*** Bug 188772 has been marked as a duplicate of this bug. ***