When your code is compiling, with no errors.

Writes code in C
Terminal: Seg fault
Rewrites code
Terminal: Seg fault
Rewrites again, opens gdb:
Seg fault

"I should open a brewery, I like beer. I've always wanted to make beer, it's analogic for the most part. No seg faults, can you believe that? Perhaps even a pub next to the brewery..."

"Oh, I was doing one extra iteration in a for loop. Nevermind"

I can’t say it’s the most painful but it’s one of my recent painful lessons.

So I’m learning C and in my project I was trying to make a copy of a 2D array and I kept getting seg faults up the ass every time I tried to allocate one of the inner arrays and after a long day of debugging I realized that I was trying to allocate memory within an array that doesn’t exist so I had to create the first array then allocate memory for each inner array after.

my boss, recently: "Partner company is complaining about seg-faults in our software" [the system is still in testing, not deployment]

me: "tell me what steps to reproduce the error and I'll fix it"

boss: "I'd like to prevent seg faults from happening no matter what"

...I literally can't even at this point

aaaaaAAAAaAh segmentation faults are horrible cause its a runtime error and it wont show u where u went wrong
ive been stuck for a few days with seg faults and i just realized i havent allocated space uuuuggghh its so dumb. a simple mistake of not putting malloc() can make u go crazy for a few days

MRW my project has a 50/50 chance of executing flawlessly or hitting segmentation faults

Seems like there is a GHOST in my office, my code was working on friday, and now , the fucking seg faults