TheCee ( TheCee@programming.dev ) deleted by creator to Programming@programming.devEnglish · edit-23 years agoA Debugger Feature I'd Like To Seeceesstuff.github.ioexternal-linkmessage-square28linkfedilinkarrow-up115file-text
arrow-up115external-linkA Debugger Feature I'd Like To Seeceesstuff.github.ioTheCee ( TheCee@programming.dev ) deleted by creator to Programming@programming.devEnglish · edit-23 years agomessage-square28linkfedilinkfile-text
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.
minus-squarezygo_histo_morpheus ( zygo_histo_morpheus@programming.dev ) linkfedilinkEnglisharrow-up4·3 years agoMany 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
minus-squareTheCee ( TheCee@programming.dev ) deleted by creatorOPlinkfedilinkEnglisharrow-up3·3 years agoThat’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.
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 endThat’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.