@devilish666@lemmy.world to Programmer Humor@programming.dev • 1 year agoC++ Momentlemmy.worldimagemessage-square34fedilinkarrow-up1334arrow-down117
arrow-up1317arrow-down1imageC++ Momentlemmy.world@devilish666@lemmy.world to Programmer Humor@programming.dev • 1 year agomessage-square34fedilink
minus-square@DannyBoy@sh.itjust.workslinkfedilinkEnglish16•1 year agoIt’s been a minute since I used C/Cpp but if you compile with debugging symbols and using gdb give you info like in Java? At least the location of the crash.
minus-square@Miaou@jlai.lulinkfedilink13•1 year agoAnd then you realise the program doesn’t crash when compiling with debug symbols 😢
minus-square@Buddahriffic@lemmy.worldlinkfedilink8•1 year agoThen it’s time to have a closer look at how your concurrent threads are behaving and where you missed a sync point or mutex.
minus-square@mrkite@programming.devlinkfedilink4•1 year agoThat’s when you break out valgrind because you certainly are using uninitialized memory.
minus-squareZiglin (it/they)linkfedilink2•1 year agoAnd much more, it tells you each operation it goes through, where it is in the code, what’s in the registers and more.
It’s been a minute since I used C/Cpp but if you compile with debugging symbols and using gdb give you info like in Java? At least the location of the crash.
And then you realise the program doesn’t crash when compiling with debug symbols 😢
Then it’s time to have a closer look at how your concurrent threads are behaving and where you missed a sync point or mutex.
That’s when you break out valgrind because you certainly are using uninitialized memory.
And much more, it tells you each operation it goes through, where it is in the code, what’s in the registers and more.