Bug 57301 - JDT editor crashed my JVM after I typed /** plus Enter
Summary: JDT editor crashed my JVM after I typed /** plus Enter
Status: RESOLVED DUPLICATE of bug 56390
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Felipe Heidrich CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-02 15:00 EST by Allan Pratt CLA
Modified: 2004-04-23 16:20 EDT (History)
2 users (show)

See Also:

Attachments
The javacore dump file from this crash (735.85 KB, text/plain)
2004-04-05 12:41 EDT, Allan Pratt 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 Allan Pratt CLA 2004-04-02 15:00:18 EST 
This is a "random instability" bug report, because this is not reproducible. 
I'm using the final M8 version of WSWB, and after using one Eclipse session for 
a while, including debugging and hot code replace (with IBM's J9 JVM), I added 
a field to a class and then typed "/**" and hit Enter to fill out the JavaDoc 
style comment.

This is on Windows, and I got an access violation: The instruction at 
0x000e1107 referenced memory at 0x00000001. Starting MS Visual Studio on the 
javaw process showed that address 0x000exxxx is outside all loaded modules, and 
in fact it is a data area consisting mainly of words with the value 0x0060 and 
0x0020. So obviously the problem was a wild jump into data.

Some addresses at negative offsets from SP lie in the address range of 
NTDLL.DLL and KERNEL32.DLL, but the nearest one that makes sense is in ZIP.DLL 
and that doesn't seem very likely.
Comment 1 Dirk Baeumer CLA 2004-04-04 12:53:37 EDT 
Moving to SWT (Styled Text got recoded for M8).
Comment 2 Grant Gayed CLA 2004-04-05 11:55:16 EDT 
Can you attach the dump file?
Comment 3 Allan Pratt CLA 2004-04-05 12:41:56 EDT 
Created attachment 9220 [details]
The javacore dump file from this crash

This is the javadump file from the crash.
Comment 4 Grant Gayed CLA 2004-04-15 11:06:33 EDT 
SSQ, the trace doesn't give much insight into what was happening in main at the 
time of the crash.  Could be J9 related?
Comment 5 Silenio Quarti CLA 2004-04-15 14:23:45 EDT 
Please could you try the latest integration build? We have fixed a segment 
fault on Windows, which might be the same as yours.
Comment 6 Allan Pratt CLA 2004-04-15 16:03:59 EDT 
This problem is not repeatable, so "trying" a new build won't help. All I can 
do is report if it happens again.
Comment 7 Felipe Heidrich CLA 2004-04-23 16:20:57 EDT 
Please, reopen this if it happens again.

*** This bug has been marked as a duplicate of 56390 ***