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

Bug 36100

Summary: Initiating remote debug session against Sun's WTK 2.0 causes a memory access violation
Product: [Eclipse Project] JDT Reporter: Yuri Magrisso <yumariso>
Component: DebugAssignee: Jared Burns <jared_burns>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P4 CC: Darin_Swanson, eclipse-bugzilla, ed.burnette, maffeis
Version: 2.1Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:
Attachments:
Description Flags
zip file with full Eclipse project with debug scripts and logs
none
Copy of dos output - launch demo in debug mode none

Description Yuri Magrisso CLA 2003-04-05 07:01:29 EST
When I initiate a remote debug session against Sun's WTK 2.0 (with the -Xverbose
flag) I receive the following error message:
zayit.exe - Application Error <window title>
The instruction at "0x0000000a" referenced memory at "0x0000000a". The memory
could not be "read".

When I initiate it without this flag the message reads:
zayit.exe - Application Error <window title>
The instruction at "0x0042a9fa" referenced memory at "0x0000001c". The memory
could not be "read".

I receive similar error messages when I use WTK 1.0.4, or Eclipse 2.0.2.
The MIDlet that I try to debug is a "Hello World" application.

The jar/jad files are created with antenna 0.9.8 (http://antenna.sourceforge.net)

Except for the antenna debug target, I have attached 3 debug batch files and
their corresponding output logs (debug.bat >> debug.log, debug1.bat >>
debug1.log, etc.). The output of the antenna debug target is the same as in
debug2.log.

For any questions write to yumariso@fastmail.fm.

Regards,
Yuri Magrisso
Comment 1 Yuri Magrisso CLA 2003-04-05 07:03:28 EST
Created attachment 4473 [details]
zip file with full Eclipse project with debug scripts and logs
Comment 2 Daniele Gariboldi CLA 2003-04-08 06:12:44 EDT
Created attachment 4490 [details]
Copy of dos output - launch demo in debug mode

I have the same problem (eclipse 2.1 - win nt - 1.4.1-rc).
I launch the demo apps of J2ME-WTK2.0 using the following modified .bat.
The attachment is the output of that .bat.

rem Modified run.bat  to debug demo apps
set PROJBINDIR=..\apps\demos\bin
@echo on
cd ..\..\..\bin
emulator  -Xverbose:all -Xdebug
-Xrunjdwp:transport=dt_socket,address=5000,server=y -classpath
%PROJBINDIR%\demos.jar -Xdescriptor:%PROJBINDIR%\demos.jad
cd %PROJBINDIR%
Comment 3 Jared Burns CLA 2003-09-17 13:10:40 EDT
Going with "not our bug" on this one.

We just connect to the WTK following the JDWP protocol standard. If the VM 
crashes in response to this, it's pretty clear that this is a problem with the 
KVM.

I suggest opening a bug report against the WTK vendor.