News for hackers. Stuff that matters.
Re:What is a coder's worst nightmare? (2014) by jacquesm on Sunday November 22, 2015 @01:14AM (#10609251)
Is this on a unix machine?

If so crash the program with a kill -9 set up to write the core to disk, then run gdb on the executable and reload that core file. Then run 'where'. This will tell you where you're hanging and how you got there as well as all the parameters to functions on the way down.

A ps -aux beforehand can give you another hint, look at the status letter.

Good luck!

Re:What is a coder's worst nightmare? (2014) by danieltillett on Sunday November 22, 2015 @04:55AM (#10609619)
I have a Linux version, but unfortunately the version that stops is the Windows version. At this point if I solve this it is going to be by chance.
Re:What is a coder's worst nightmare? (2014) by jacquesm on Sunday November 22, 2015 @09:52AM (#10610195)
Ai, in that case I have no bag-of-tricks for you, my last windows programming was about a decade ago and I don't miss it in the least. Much good luck, if you ever do figure out what caused it you should definitely do a write-up, there is probably a more general lesson to be learned from nailing that one down.
Re:What is a coder's worst nightmare? (2014) by xorcist on Sunday November 22, 2015 @03:23AM (#10609449)
ps aux (the dash is for sysv syntax: ps -eif)
Re:What is a coder's worst nightmare? (2014) by jacquesm on Sunday November 22, 2015 @06:18PM (#10611957)
Aargh. Sorry about that. It's so easy to mess that one up. Gets me with tar all the time as well. Thanks for the correction.