{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/29/2021 10:54:25 PM
2
I've cursed many times in my programming classes when trying to figure out why I get a buffer overflow. 🤣
Segment faults with no obvious cause are even more annoying.
English
-
Back in my day, we coded in raw assembly languages and unprotected pointers were far more common than these days. References didn't even exist yet, nor did tools for spotting memory corruption. Usually things would just freeze with almost no indication of what was wrong. Lots of "fun" bugs that the programmers of the day had to become masters at avoiding or spotting quickly.
-
One of the funniest typos I have had was not realizing a 1 was supposed to be an I. The font made it really hard to see. Literally had to walk away and come back to spot it.
-
Edited by XiiDraco: 8/29/2021 10:58:54 PMHahaha. I love seeing someone get a heap corruption for the first time and try and track it down with prints or stepping through debug only to find the magic floaty point where the system detects the corruption. Their face when I tell them that the system detecting the corruption and the actually corruption happening aren't the same place is absolutely priceless. Using a mem checking tool like valgrind has been amazing for me. Especially with WSL, because valgrind is waaaay better than Dr. memory and WSL is super easy to setup and use with CLion.
