@devilish666 to Programmer [email protected] • 10 months agoC++ Momentimagemessage-square34arrow-up1334arrow-down116
arrow-up1318arrow-down1imageC++ Moment@devilish666 to Programmer [email protected] • 10 months agomessage-square34
minus-square@[email protected]linkfedilinkEnglish16•10 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-square@[email protected]linkfedilink13•10 months agoAnd then you realise the program doesn’t crash when compiling with debug symbols 😢
minus-square@Buddahrifficlink8•10 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-square@[email protected]linkfedilink4•10 months agoThat’s when you break out valgrind because you certainly are using uninitialized memory.
minus-squareZiglin (they/them)link2•10 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.
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.