>run program >segmentation fault >run program again

Utilized a non-problematic section of memory on the 2nd run

your input changed

>>62303677
How come?

>>62303714
Literally ran the program again.

If your shit is multithreaded, you might have some race conditions

>>62303632
you probably have a race condition on a variable you're using to index memory

sudo apt-get install valgrind

>>62303632
One case could be the null terminator of a string. First time, there was no zero found outside the allocated space, but there was on the second time.

File: nene can't code for shit.jpg (204KB, 496x1122px) Image search: [Google]

204KB, 496x1122px

>>62303632
Is this you?

>>62303775
>>62303820
>you might have some race conditions
>you probably have a race condition

wow... I didn't think that race was going to be brought into question here.

File: e49d77df2f418eb33a63e8c12cb4084e.jpg (27KB, 600x315px) Image search: [Google]

27KB, 600x315px

>>62303848
I'm the only black programmer in my company, and now that you mentioned the other coders don't run in these kind of problems as often. I guess C++ is racist.

>>62303848
nice dude

>>62303632
uninitialized automatic variable
used for memory indexing

File: Screenshot at 2017-09-05 23:09:42.png (192KB, 1680x1002px) Image search: [Google]

192KB, 1680x1002px

shit out some mallocs into your code

>>62303838
Why is she going to shit if she sees another keyboard though?

>when your code directory is filled with core dumps