Hacker News new | past | comments | ask | show | jobs | submit login

Just

  catch infinite-loop
in gdb and you're done!



Would anyone know how that works internally? Sounds very useful


Sadly it does not work at all, as it was a joke :/.

But I did think about how it could work. It could work by peridically sampling the instructions the current thread is running and detect trivial infinite loops that way.

With more effort more complicated infinite loops could be detected, but in the end not all, due to the halting problem.

edit: Actually maybe halting problem is not (theoretically) involved if you have a lot of memory: take snapshots every after every instruction. Once you take a snapshot you have already taken previously, you have found a loop. However you would still might need to somehow account for (emulate and include in snapshot?) or disallow external IO, such as time of day.


QuakeC automatically detected "infinite" loops (actually >100k loops). It was very useful!




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: