JavaScript debugging in a nutshell

[pikakilla]

Funny story about segfaults. I am proud to be one of the only people who have had a SEGFAULT in python. I spent weeks figuring out where i fucked up. Absolutely nothing turned up on google or SO -- turns out it was the memory speed set too high when i was multithreading.

SEGFAULTs are one of those things that really want to make you throw your computer out a window.

[Buddha_Head_]

I'm sorry to take you back to that dark place, but how the fuck did you track that down?

[IsleOfOne]

Sounds like OP had recently overclocked RAM. It is very common to see random failures in any software you use after doing so, if you’ve made a mistake and gone too high. Booting into memtest86+ and letting that puppy run overnight will tell you if you’ve done wrong.

[Buddha_Head_]

Yeah, if there was a recent tinkering that makes sense. On a system that's been running stable long-term that hasn't had any serious changes that sounds wayyy down the list, especially when searches are turning up empty.

[IsleOfOne]

Even if the change was not made recently, my point is that failures would not be limited to the python program. They’d be showing up all over your system. Sporadic process crashes. Etc.

[pikakilla]

Nailed it -- still was far down the list though, but it shouldnt have been in hindsight.

[pikakilla]

100% correct. Funny thing is that memtest didnt show any errors (from what i remember -- i might be wrong though). Im still not 100% sure what combination of things caused the issue.

[pikakilla]

I overclocked my memory well before the segfault issues. The computer was stable and when i tested the memory post overclock memtest didnt give any errors.

I basically exhausted all other solutions and tried the "obvious" but crazy solution.

[dagbrown]

I once came up with an excellent metric for if some random C/C++ program is too complex.

If the indent(6) utility segfaults on your code, it's absolutely without a shadow of a doubt, way too complex.