Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: Scala 2.10.0-M6
    • Fix Version/s: Backlog
    • Component/s: Compiler Backend
    • Labels:
      None

      Description

      this is a less severe form of SI-6049. SI-6049 was closed because the back end no longer crashes, but there are still spurious warnings.

      so e.g. borrowing Miguel's minimized code from SI-6049:

      Welcome to Scala version 2.10.0-M6 (Java HotSpot(TM) 64-Bit Server VM, Java 1.6.0_33).
      
      scala> :paste
      object O {
        while(true) {
          var j = 0
          try j
          catch { case t: Throwable => }
        }
      }
      // Exiting paste mode, now interpreting.
      
      <console>:11: warning: Visited SCOPE_EXIT before visiting corresponding SCOPE_ENTER. SI-6049
                 try j
                 ^
      defined module O
      

      at SI-6049 Miguel said this warning could also be a sign of issues with "whether the debugger shows the variable in question"

        Issue Links

          Activity

          Hide
          Adriaan Moors added a comment -

          Debug info still needs to be improved, but the warning is nog longer emitted by default.

          Show
          Adriaan Moors added a comment - Debug info still needs to be improved, but the warning is nog longer emitted by default.
          Hide
          Seth Tisue added a comment -

          fix version is...?

          Show
          Seth Tisue added a comment - fix version is...?
          Hide
          Adriaan Moors added a comment -

          2.11.x? This didn't seem urgent?

          Show
          Adriaan Moors added a comment - 2.11.x? This didn't seem urgent?
          Hide
          Seth Tisue added a comment -

          the ticket is closed as fixed. essentially, I'm asking what branch the fix has already been made on. (I'm not suggesting a 2.10.x backport)

          Show
          Seth Tisue added a comment - the ticket is closed as fixed. essentially, I'm asking what branch the fix has already been made on. (I'm not suggesting a 2.10.x backport)
          Hide
          Adriaan Moors added a comment -

          Oh, I was thinking we were fixing it in the future. Looks like an accidental close – I really need SI-autocorrect.

          Show
          Adriaan Moors added a comment - Oh, I was thinking we were fixing it in the future. Looks like an accidental close – I really need SI-autocorrect.

            People

            • Assignee:
              Jason Zaugg
              Reporter:
              Seth Tisue
            • Votes:
              9 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:

                Development