Programming

17394 readers

162 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

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

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

A Debugger Feature I'd Like To See (ceesstuff.github.io)

submitted 1 year ago* (last edited 1 year ago) by TheCee@programming.dev to c/programming@programming.dev

26 comments fedilink hide all child comments

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

[–] DigitalBits@lemmy.fmhy.ml 2 points 1 year ago

Ah, I see. I didn't see the bit about it being a breakpoint (detour point?). That's what I get for skim reading rather than comprehending it. Visual studio will let you do this, but it's a manual step, by combining a normal breakpoint and an execute next statement, and you'd have to do this each time you hit the breakpoint.

Having it happen automatically? A fairly niche feature, but I can see a few uses for it. The component features are already there, so I don't think it would be difficult to implement in a debugger that already supported execute next statement.