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:
debug
Intel® Debugger for Linux* (IDB)
The Intel® Debugger is an Eclipse Rich Client Platform based GUI driven Debugger with exciting features for parallelism and threading.
Debug Solutions Support Articles
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
Debugging Yocto Project* Applications with Intel® Debugger
Rare Stack Overflow Occurs in Windows* IA-32 Debug Mode
In rare cases, a stack overflow can occur in Windows* IA-32 debug mode. A workaround is provided for IA-32 release mode and Intel® 64 debug/release modes.
I just discovered Valgrind, it's about time.
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.
Understanding Intel® Cluster Checker Debug Output and the Secure Shell (SSH)
This article describes how to interpret debug output from the Intel Cluster Checker.
Use of PCH and /Zi with Boost* Libraries May Result in unresolved external symbols due to Anonymous Namespace Use
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.
Seiten
