this post was submitted on 26 Jun 2023
19 points (100.0% liked)

Programming

17398 readers
105 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] bad_alloc@feddit.de 4 points 1 year ago (1 children)

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.dev 1 points 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.