Bug 383975 - Debugger: Don't stop at breakpoints at lines with multiple statements
Summary: Debugger: Don't stop at breakpoints at lines with multiple statements
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-30 20:27 EDT by Boris Brodski CLA
Modified: 2012-06-30 20:27 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Brodski CLA 2012-06-30 20:27:03 EDT
Eclipse don't stop at a breakpoints, if "to much" model elements written at one line.

Reproduction with Xbase.

Create a brand new Domainmodel-example project and run it.
In the second eclipse instance create a model file and write:

package a {
  entity B {
    op my (String name) : String {
      var b = {var x = ""; ""} ; ""
    }
  }
}

Set a breakpoint at the line 4 ("var b = ..."). Write a simple Test class with a main method calling my() method defined in the model. Run the Test class in the debug mode. Eclipse will NOT stop at the breakpoint. Change the line 4 to

      var b = {var x = ""; ""}
      ""
Run the Test class in the debug mode again. Eclipse WILL stop at the breakpoint (line 4).


This bug affects not only Xbase, but also custom DSLs.

It looks like multiple "trace(o, true)" calls for an objects on the same line cause the problem.