Cee's Funposts - Detour Points
ceesstuff.github.io

Hi, has anybody of you ever seen a feature as described in the post in your environment?

Thank you

Update: As some readers appear to have skimmed the text, please feel free to point out possible accessibility issues, poor choices of words, etc.

  • @bad_allocEnglish
    4•1 year ago

    Interesting idea! Although it seems to be very invasive. If it really detours code the breakpoint suddenly modifies execution. Most debuggers seem to bebuilt as pure measurement tools. And i have the feeling for good reason: Understanding when the code will be executed is a big part of debugging. And the need to detour suggests the code is poorly debuggable.

    • @TheCee@programming.devOPEnglish
      1•1 year ago

      And i have the feeling for good reason: Understanding when the code will be executed is a big part of debugging.

      True. If I forget the detour points from a previous debugging session, I’m going to have a bad time.

      And the need to detour suggests the code is poorly debuggable.

      Indeed. Unfortunately that’s nothing you get to choose, so, the more important are better tools.