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

Close

#14 Debugger-Error

closed
nobody
None
5
2007-09-21
2007-06-27
Anonymous
No

Hello,

as I promissed, I will test Kontrollerlab. First of all I would like to thank you for the great improvements you've done. Your're great!

But, unfortunatelly the debugger is a always hanging up on my computer. I've submitted (added) here my simple testfile and I hope you can help me.

Thanks

Michael

Discussion

  • the testfile

     
    Attachments
  • Logged In: YES
    user_id=902327
    Originator: NO

    I will test it ASAP.

    Till soon,
    cadManiac

     
  • Logged In: YES
    user_id=902327
    Originator: NO

    Fixed with revision 151.

    The changed files are:
    src/kldebugger.cpp
    src/kldebugger.h

    The fix is:
    The flag m_atLeastOneSrcLine tells us if there was at least one line which is visible to the user in KLab. This is important if the user presses "step over" before the first line was executed, because the call counter can be wrong then and then the stepping never finishes.
    Example: A call to the main routine -> call counter is 1, m_stopCallCounter would be 0 -> no return!
    To avoid this, m_atLeastOneSrcLine is checked and if it is false and a visible line is encountered, we set the m_stopCallCounter to the current value of m_cpu.callCounter().

     
    • status: open --> closed
     
  • overt2here
    overt2here
    2007-07-14

    Logged In: YES
    user_id=1664921
    Originator: NO

    Thanks!

     
  • overt2here
    overt2here
    2007-07-14

    • status: closed --> open
     
    • status: open --> closed