| [#653] | project: compiler | priority: low | category: bug | |
|---|---|---|---|---|
| submitter | assigned to | status | date submitted | |
| Sean | Iulian | fixed | 2006-07-11 16:05:27.0 | |
| subject | assert line number info | |||
| code |
object Test {
def main(args : Array[String]) : Unit = {
Console.println("BEGIN");
assert(1 > 0);
Console.println("BEGIN");
assert(f);
Console.println("END");
assert(f);
}
def f = true;
}
|
|||
| what happened | In debugger, when stepping around (not in), will always step to top of enclosing class before stepping to assert\ statement. |
|||
| what expected | assert statements should be constrained into one line and their debug line number info should not include the top of the enclosing class. | |||
| [back to overview] | ||||
| Iulian edited on 2006-07-11 17:27:01.0 |
| This one I cannot reproduce (yet), but I also noticed some weird behavior. In some cases Positions.line(pos) would fail (throw an exception) in the backend, because the source file length would be less than the given position! This indicates some 'cross-file' positions in the source code (probably a different bug than this one, though..). |
| Iulian edited on 2006-07-12 10:52:38.0 |
| Refcheck transforms 'assert(something)' to 'scala.this.Predef.assert(something)'. The additional path is positioned wrongly. |
| Sean edited on 2006-07-17 13:24:32.0 |