Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#2 My BreakPoint is moving but not :)

closed
Riaan Booysen
None
3
2003-11-10
2001-03-21
InnerCircle
No

In Boa 0.05 (Witch is astonishing me each time I
launch it :)) when you set a breakpoint (with F5) and
add further components the breakpoint stay on the
orginal line number that is no more assigned to the
original line.... It should probably move with the
line ;)

Discussion

  • Logged In: YES
    user_id=144122

    yes the debugger is making yet still troubles, we know
    this problem.
    I don't know yet whether we are making a hotfix for this,
    since we are planning to overwork the whole debugger in
    the next release.
    Next release should be a merge of the "new debugger" and
    "zoa" branch in cvs which will bring improved and more
    features for debugging and zope support.
    thanks robert

     
  • Riaan Booysen
    Riaan Booysen
    2001-04-09

    Logged In: YES
    user_id=438

    Thanks!

    This is problem which will need some work.
    (also needed for the new debugger)
    The fix will have the (maybe not directly obvious) benefit
    of improving code completion accuracy.

    Should be finished before the next release.

     
  • Riaan Booysen
    Riaan Booysen
    2001-04-09

    • assigned_to: nobody --> riaan
    • priority: 5 --> 7
    • status: open --> open-accepted
     
  • Riaan Booysen
    Riaan Booysen
    2001-07-16

    Logged In: YES
    user_id=438

    Just adding a note to show that I have not forgotten this. It's a trickier problem than I once thought.
    See progress so far on this issue in Views.PySourceView.OnModify

    The biggest fundamental problem at them moment is that certain operations on a file in the editor replaces the
    whole file's contents (as opposed to being able to track that e.g. 5 lines were inserted at line number 75, such
    changes I can track and handle)

    When the whole contents is replaced in one go, context is lost. Without doing some kind of diff, it's difficult to
    know if the breakpoint moved up or down. We could for now just adjust code markers (breakpoints) with
    trackable changes. Only whole code replacements will then cause breakpoints to get out of sync (by then staying
    on the same place while the code moved under it.)

    I'll try this soon...

     
  • Riaan Booysen
    Riaan Booysen
    2001-08-06

    • priority: 7 --> 3
    • assigned_to: riaan --> nobody
    • status: open-accepted --> open-postponed
     
  • Riaan Booysen
    Riaan Booysen
    2001-08-06

    Logged In: YES
    user_id=438

    I've come back to this problem again (and again)

    This is not actually a bug because it is not legal to change your code while debugging (the source image being
    debugged will stay the same so if the breakpoints move they are out of sync)

    Yet the current behaviour is also confusing and it is not entirely clear to me what the correct behaviour should be.

     
  • Riaan Booysen
    Riaan Booysen
    2003-11-10

    Logged In: YES
    user_id=438

    I'm closing this issue as tracking breakpoint is now as solid as
    I can get it.

    Riaan.

     
  • Riaan Booysen
    Riaan Booysen
    2003-11-10

    • assigned_to: nobody --> riaan
    • status: open-postponed --> closed