> Hangs could be so many things, but it is the absence of information. start adding information. you need to know what the code is getting to and/or what its

> Hangs could be so many things, but it is the absence of information. start adding information. you need to know what the code is getting to and/or what its not getting to and progressively narrow it down. spamming debug print statements can be useful if you have no better ideas to get yourself moving. or if you can manage to hook up an interrupt handler to be able to get it to dump a stack trace that'll immediately tell you. or attach a debugger while its spinning in order to get a stack trace. or attach something like strace to dump out system calls or ltrace to dump out libc calls. that can't catch processing spinning in "math" though, but that absence of information is a hint that eliminates lots of possibilities. you may need to add a feature to the software in order to do this kind of debugging, so you write your own USR1 interrupt handler or something. it will be worth it. i think the kids these days use stuff like systemtap?