4 ms·
I have one of those random concurrency bugs in my code right now - it takes a month to show up and so far not in the debug build. The code doesn't crash, the pr
by danieltillett 11y ago
I have one of those random concurrency bugs in my code right now - it takes a month to show up and so far not in the debug build. The code doesn't crash, the program just stops running as though manually paused.
- paulrd 11y agoThis reminds me of the buggy pic-C compiler standard library I was using. Some functions calls with particular parameters (maybe the printf family) would halt program for no apparent reason.
- jacquesm 11y agoIs 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!
- danieltillett 11y agoI 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.
- jacquesm 11y agoAi, 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.
- xorcist 11y agops aux (the dash is for sysv syntax: ps -eif)
- jacquesm 11y agoAargh. 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.