Bugzilla – Full Text Bug Listing
| Summary: | Incorrect "version" attribute value in libraryInfos.xml when using .hotspot_compiler | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Pavel Zuev <pzuev> | ||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | darin.eclipse, liree, mwood, Olivier_Thomann | ||||
| Version: | 3.4 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Pavel Zuev
Created attachment 103332 [details]
Sample libraryInfos.xml
Move to JDT/Debug Short: I'd like to see it commented as hard to solve, no time left, or fixed since it affects many developers (in my opinion). LONG: Ok, I tried the voting system, however no possibility (perceived) to add a comment, so I'll comment my Intention here. The described error even occurres on a Linux system. I voted, because each time I add a VM, I have to adjust this file (libraryInfos.xml). I know of this bug and how to solve it. But many other developers do capitulate to this issue and reinstall eclipse completely if strange Errors occurr. (Even I do if I don't find a sollution in time, depending on the priority of my current work) AND the error messages do not really indicate what happened. (I use the -server flag on which the .hotspot_compiler becomes mandatory on my installations (WindowsXP, gentoo linux), because I try to max out performance everywhere, because I'm using most of the "super duper" features of eclipse [e.g. completion]) Maybe someone could point me to the souce code location where the addition of new VM's happens. Maybe I can find the sollution an submit a patch. Maybe :) (In reply to comment #3) > I'd like to see it commented as hard to solve, no time left, or fixed since it > affects many developers (in my opinion). We have very limited resources working on debug. Does not sound hard to solve. > Maybe someone could point me to the souce code location where the addition of > new VM's happens. Maybe I can find the sollution an submit a patch. Maybe :) The plug-in to look at is: org.eclipse.jdt.launching The class to look at is: StandardVMType (org.eclipse.jdt.internal.launching) The method to look at is: generateLibraryInfo(...) I'm not able to reproduce using 1.6.0_04 or the latest 1.6.0_14. It happens here too. eclipse.buildId=I20080617-2000 java.version=1.6.0_15 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: Command-line arguments: -os linux -ws gtk -arch x86 Also spotted here: http://todd.wallentine.com/blog/?p=317 It's a small but recurring problem for me, as I work on Mavenized trees of projects, If I have more than one copy of the same tree in a single workspace (and I have many copies, working several issues at once) the Maven Eclipse plugin tends to find a project's internal dependencies in seemingly randomly-selected trees, so I make new workspaces quite often to prevent that. 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. |