| 
| HotSwap w/ remote debugging ("Obsolete methods on the stack") [message #209311] | Fri, 08 July 2005 15:05  |  | 
| Eclipse User  |  |  |  |  | Is it possible to use hotswap while doing remote debugging? 
 I am currently attempting to do so, and not seeing the expected results.
 
 Here is how I am testing things out.
 1. I build the application in Eclipse
 2. I drop to the DOS prompt and start the application with ANT (I don't
 compile, I am using the class files that I built with Eclipse.  ANT is
 just creating the classpath and launching the VM)
 <jvmarg value="-Xdebug" />
 <jvmarg value="-Xrunjdwp:transport=dt_socket,server=y,address=8000" />
 3. I go back to Eclipse and attach to the remote process.
 4. A break point is hit.
 5. I go down two lines in the code and add a System.out.println statement
 for testing
 6. I save the file (Build Automatically is turned on)
 7. I get an error dialog titled "Obsolete methods on the stack"
 "Java HotSpot(TM) Client VM[localhost:8000] contains obsolete methods.
 
 Reason:
 The virtual machine was unable to remove all stack from running old code
 from the call stack.  The virtual machine is not supplying the debugger
 with valid data for those frames.  Stepping into these obsolete frames may
 be hazardous to the target virtual machine.
 
 Any help is appreciated.
 
 PS.  I am using java version "1.4.2_03"
 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
 Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) on Windows
 |  |  |  | 
| 
| Re: HotSwap w/ remote debugging ("Obsolete methods on the stack") [message #209318 is a reply to message #209311] | Fri, 08 July 2005 15:33   |  | 
| Eclipse User  |  |  |  |  | As stated in the reason for the hotswap failure...it is the VM that is disallowing whatever change you are making and it results in a unstable
 state for the virtual machine.
 There really is nothing Eclipse can do about this. You could try a different
 VM
 
 Depending on where you are adding the System.out statement in the stack (in
 the main method, after a native call, in a inner class, ...) , the VM will
 not be happy after the change.
 
 hth
 Darins
 
 "James Leone" <jleone@sjm.com> wrote in message
 news:456bf823f2c648051d94a7c4f02f5fbf$1@www.eclipse.org...
 > Is it possible to use hotswap while doing remote debugging?
 >
 > I am currently attempting to do so, and not seeing the expected results.
 >
 > Here is how I am testing things out.
 > 1. I build the application in Eclipse
 > 2. I drop to the DOS prompt and start the application with ANT (I don't
 > compile, I am using the class files that I built with Eclipse.  ANT is
 > just creating the classpath and launching the VM)
 > <jvmarg value="-Xdebug" />
 > <jvmarg value="-Xrunjdwp:transport=dt_socket,server=y,address=8000" />
 > 3. I go back to Eclipse and attach to the remote process.
 > 4. A break point is hit.
 > 5. I go down two lines in the code and add a System.out.println statement
 > for testing
 > 6. I save the file (Build Automatically is turned on)
 > 7. I get an error dialog titled "Obsolete methods on the stack"
 > "Java HotSpot(TM) Client VM[localhost:8000] contains obsolete methods.
 >
 > Reason:
 > The virtual machine was unable to remove all stack from running old code
 > from the call stack.  The virtual machine is not supplying the debugger
 > with valid data for those frames.  Stepping into these obsolete frames may
 > be hazardous to the target virtual machine.
 >
 > Any help is appreciated.
 >
 > PS.  I am using java version "1.4.2_03"
 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
 > Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) on Windows
 >
 |  |  |  | 
|  | 
|  | 
|  | 
Powered by 
FUDForum. Page generated in 0.04121 seconds