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

Bug 332885

Summary:

Difference in eclipse.ini parsing on 32 bit and 64 bit versions

Product:

[Eclipse Project] Equinox

Reporter:

Prashant Deva <prashant.deva>

Component:

Launcher

Assignee:

Project Inbox <equinox.launcher-inbox>

Status:

RESOLVED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

aniefer, remy.suen, tjwatson

Version:

3.6.1

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
ini file for 64 bit eclipse	none
ini file for 32 bit eclipse	none

Description Prashant Deva

2010-12-18 04:10:16 EST

I tried the following test on win 7 64 bit using 32bit and 64 bit versions of eclipse 3.6.1.

I edited the eclipse.ini of each to add the following 2 lines to the end of the file -

-javaagent:"recorder-1.0.0.590.jar"="recconfig.txt" 
-agentpath:"recorderagent64-1.0.0.dll"


On 64 bit eclipse this runs fine.

However with 32 bit eclipse on 64bit windows, eclipse wont start until i removed the quotes from the arguments.

Comment 1 Remy Suen

2010-12-18 09:25:00 EST

Please provide your entire eclipse.ini file.

Comment 2 Prashant Deva

2010-12-18 17:14:09 EST

Created attachment 185487 [details]
ini file for 64 bit eclipse

This works even with the quotes in the last 2 lines

Comment 3 Prashant Deva

2010-12-18 17:15:47 EST

Created attachment 185488 [details]
ini file for 32 bit eclipse

This wont work unless the quotes from the last 2 lines are removed.

This was tested on win 7 64 btw with 32 bit eclipse 3.6.1

Comment 4 Remy Suen

2010-12-19 12:25:54 EST

If you start Eclipse with the JVM directly instead of using the eclipse.exe binary and pass those JVM aruments in, does it work?

Comment 5 Prashant Deva

2010-12-19 12:27:14 EST

yes. as i said the error seems to be in parsing the eclipse.ini file. if i just remove the quotes they work. The problem is not with the jvm arguments themselves.

Comment 6 Remy Suen

2010-12-19 12:30:13 EST

(In reply to comment #5)
> yes. as i said the error seems to be in parsing the eclipse.ini file.

Yes, I realize that. But I wanted to confirm if the parsing was the problem or whether the JVM itself was not capable of handling the quotation marks.

Which JVM are you using? HotSpot from Oracle?

Comment 7 Prashant Deva

2010-12-19 12:32:27 EST

Hotspot jvm version 6 update 23.

The jvm can handle the quotes.

Comment 8 Andrew Niefer

2010-12-20 11:03:02 EST

Can you try starting from the console with
eclipsec -debug

This should print out the arguments the launcher is passing to the vm.  Then we can compare the 32 vs 64 to see if there is a difference.

Comment 9 Eclipse Genie

2019-07-12 15:42:01 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 10 Thomas Watson

2019-07-15 10:28:15 EDT

We no longer support 32 bit launchers.