devilish666@lemmy.world to Programmer Humor@programming.dev · 6 months agoC++ Momentlemmy.worldimagemessage-square22fedilinkarrow-up116arrow-down13
arrow-up113arrow-down1imageC++ Momentlemmy.worlddevilish666@lemmy.world to Programmer Humor@programming.dev · 6 months agomessage-square22fedilink
minus-squareDannyBoy@sh.itjust.workslinkfedilinkEnglisharrow-up1·6 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-up2·5 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-up1·6 months agoAnd then you realise the program doesn’t crash when compiling with debug symbols 😢
minus-squaremrkite@programming.devlinkfedilinkarrow-up2·6 months agoThat’s when you break out valgrind because you certainly are using uninitialized memory.
minus-squareBuddahriffic@lemmy.worldlinkfedilinkarrow-up1·6 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.
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 😢
That’s when you break out valgrind because you certainly are using uninitialized memory.
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.