Bugzilla – Full Text Bug Listing
| Summary: | JITC access violation while typing in JDT editor | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Allan Pratt <apratt> |
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Keywords: | needinfo |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| See Also: | https://git.eclipse.org/r/c/orbit/orbit-recipes/+/192553 | ||
| Whiteboard: | |||
Please file the bug against the VM. Get rid of deprecated state. . New Gerrit change created: https://git.eclipse.org/r/c/orbit/orbit-recipes/+/192553 |
I am using WSWB from the 3/31 build - that is, M8 final. I was typing away in my Java editor when I got an access violation: the instruction at 0x02273692 tried to read memory at address 0x1. The instruction is inside the code space of the JITC.DLL library. Since I'm using WSWB M8, the JITC in question is from the IBM Classic (not J9) JVM. The MS Visual Studio debugger stack traceback shows this: JITC! fi_init + 354 bytes JVM! 100d26ae() and nothing else. Of course this is a JVM bug instead of a JDT crash, but the result is that it makes the JDT appear unstable so I'm filing it here. Maybe somebody will see a pattern in crash reports like this, and take it the next step.