Programming

17398 readers

205 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

17 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

[–] zygo_histo_morpheus@programming.dev 4 points 1 year ago (1 children)

Many debuggers have a set next statement kind type of functionality, but with gdb you can script it so that it performs the jump automatically, like the article suggests:

break 1
commands
jump +3
end

[–] TheCee@programming.dev 3 points 1 year ago

That's pretty cool. I always wondered why gdb has a scripting interface, now I'm curious what other cool user scripts one can do through it.