Last year, I wrote a blog about creating your own simple collision detection code. I implemented this for a children's math game I created. You can refer to my blog here:
articles and whitepapers covering Intel's debuggers and enhancements to 3rd party debuggers. tips, tricks,methods, bkms, and recommendations
Debugging Yocto Project* Applications with Intel® Debugger
Most of my coding career at Intel was been spend using C#, but with the mesh project, we needed to build the background peer-to-peer agent as small and as portable as possible and coding it in C made sense. Well, anything you code in raw C code, there are plenty of opportunities for problems. I have noticed that the mesh agent was not always stable and twice in the last month I saw it cause a segmentation fault. On Windows, the mesh agent runs as a service and the service manager is setup so it can restart the agent if anything goes wrong, but that only mask the problem.
Using boost::bind with placeholders like _1 with precompiled headers containing includes of boost/bind may generate an unresolved external symbol on the placeholder when debug generation is enabled.