devilish666@lemmy.world to Programmer Humor@programming.dev · 9 个月前C++ Momentlemmy.worldimagemessage-square34fedilinkarrow-up1329arrow-down117
arrow-up1312arrow-down1imageC++ Momentlemmy.worlddevilish666@lemmy.world to Programmer Humor@programming.dev · 9 个月前message-square34fedilink
minus-squareDannyBoy@sh.itjust.workslinkfedilinkEnglisharrow-up16·9 个月前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.
minus-squareMiaou@jlai.lulinkfedilinkarrow-up14arrow-down1·9 个月前And then you realise the program doesn’t crash when compiling with debug symbols 😢
minus-squareBuddahriffic@lemmy.worldlinkfedilinkarrow-up8·9 个月前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.
minus-squaremrkite@programming.devlinkfedilinkarrow-up4·9 个月前That’s when you break out valgrind because you certainly are using uninitialized memory.
minus-squareZiglin@lemmy.worldlinkfedilinkarrow-up2·8 个月前And 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.