devilish666@lemmy.world to Programmer Humor@programming.dev · 4 months agoC++ Momentlemmy.worldimagemessage-square32fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageC++ Momentlemmy.worlddevilish666@lemmy.world to Programmer Humor@programming.dev · 4 months agomessage-square32fedilink
minus-squareDannyBoy@sh.itjust.workslinkfedilinkEnglisharrow-up0·4 months 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-squareZiglin@lemmy.worldlinkfedilinkarrow-up0·3 months agoAnd much more, it tells you each operation it goes through, where it is in the code, what’s in the registers and more.
minus-squareMiaou@jlai.lulinkfedilinkarrow-up0·4 months agoAnd then you realise the program doesn’t crash when compiling with debug symbols 😢
minus-squareBuddahriffic@lemmy.worldlinkfedilinkarrow-up0·4 months 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-squaremrkite@programming.devlinkfedilinkarrow-up0·4 months agoThat’s when you break out valgrind because you certainly are using uninitialized memory.
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 much more, it tells you each operation it goes through, where it is in the code, what’s in the registers and more.
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.