Summary: | Random craches with corupt jar in library path | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Bodo Junglas <landru> | ||||||
Component: | Core | Assignee: | Kent Johnson <kent_johnson> | ||||||
Status: | RESOLVED WONTFIX | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | philippe_mulet | ||||||
Version: | 2.1 | ||||||||
Target Milestone: | 2.1 M4 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Bodo Junglas
2002-11-27 17:03:55 EST
Created attachment 2541 [details]
Probably corupt jar
I think this one is responsible, but I'm not 100% sure.
Could we improve this behavior ? Why isn't the JavaModel also crashing in similar way? Had no problem compiling against the jar file. I'm running the JDK build 1.3.1_01a. Created attachment 2581 [details]
It's most likely this one
I think my first guess was wrong. I've replaced the jdbc extensions above by a
different version that worked fine in another project and still observered the
random crashes. So I've experimented a little and observered that the workspace
seems to be stable if I remove the mysql-jdbc driver from the classpath (just
have to include it if I want to debug).
I'm not sure if this helps. The jar-File seems to be completely sane and works
fine outside the IDE with the same VM.
This problem seems to be spezial to the 1.3.1_06 jdk, since I share the project
with some collegues who have never observered this problem with a slightly
older jdk (1.3.1_03 I think)
I don't believe we can protect ourselves from natives failing, and if we could, I don't think we want to... If we silently treat the jar file as if its empty or didn't exist, we won't end up helping the user in the end. Closing as JRE bug. |