search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

[Debugger] Exception when "stepping over" #1314

Closed eclipse-ocl-bot closed 2 hours ago

eclipse-ocl-bot commented 2 hours ago

| --- | --- | | Bugzilla Link | 435408 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | May 21, 2014 10:21 EDT | | Modified | May 25, 2015 17:20 EDT | | Blocks | 435314 | | Reporter | Adolfo Sanchez-Barbudo Herrera |

Description

Steps to reproduce:

  1. Open an ecore editor such us Tutorial.ecore
  2. Select the EPackage and open the Xtext Console
  3. Introduce a simple ocl expression such "self.name.size() >0"
  4. Click on "Debug" button
  5. Press F6 (Step Over)
  6. An exception occurs and is logged in the console[1]

Note1: Stepping into (F5) works fine in this use case.\ Note2: Might it be a duplication of Bug 434199 ?

[1] Terminating execution...\ Diagnostic ERROR source=org.eclipse.ocl.examples.debug.evaluation code=120 Execution failed data=[org.eclipse.ocl.examples.debug.vm.utils.VMRuntimeException: Execution failed]\ [Java cause:]\ org.eclipse.ocl.examples.debug.vm.utils.VMRuntimeException: Execution failed\ at org.eclipse.ocl.examples.debug.vm.launching.InternalDebuggableExecutor.execute(InternalDebuggableExecutor.java:296)\ at org.eclipse.ocl.examples.debug.vm.launching.DebuggableRunner.execute(DebuggableRunner.java:112)\ at org.eclipse.ocl.examples.debug.vm.launching.DebuggableRunner$2.execute(DebuggableRunner.java:83)\ at org.eclipse.ocl.examples.debug.vm.VMVirtualMachine.execute(VMVirtualMachine.java:150)\ at org.eclipse.ocl.examples.debug.vm.VMVirtualMachine.access$11(VMVirtualMachine.java:147)\ at org.eclipse.ocl.examples.debug.vm.VMVirtualMachine$1.run(VMVirtualMachine.java:207)\ at java.lang.Thread.run(Unknown Source)\ Diagnostic ERROR source=org.eclipse.ocl.examples.debug.evaluation code=120 Execution failed data=[org.eclipse.ocl.examples.debug.vm.utils.VMRuntimeException: Execution failed]

eclipse-ocl-bot commented 2 hours ago

By Ed Willink on May 23, 2014 10:42

The maintainenace of OCLVMRootEvaluationVisitor.fCurrentLocation was wierd and I improved it (inadequately).

It can be quite simple, so now it is and it's @NonNull too so the NPE that caused the termination cannot happend again.

commit e267b48f72c0a4a292ed3f3f7fc4d217905302c1

pushed to master for RC2

eclipse-ocl-bot commented 2 hours ago

By Ed Willink on May 25, 2015 17:20

CLOSED after more than a year in the RESOLVED state.