debugging
Remote Debugging Windows 8 Apps to Intel Tablets from Ultrabook or Laptop Host
One of the first things I wanted to see when I got my new Intel Tablet was to test some of the apps I develop for my Ultrabook. Initially I packaged the app, saved to a USB drive then, inserted that into my Tablet and installed. However as I made minor tweeks and changes that solution was too cumbersome. If you are like me and do a lot of trial and error tweaking, a new build for eacg test is not a sustainable option.
Discussing Intel's OpenCL With Technical Lead Yariv Aridor - Parallel Programming Talk #117
Time for another episode of Parallel Programming Talk – This is show #117. We’ll be talking with Intel’s OpenCL Technical Lead Yariv Aridor
What is Clay thinking about today? Voice Recognition Systems - Watch the video to hear what Clay had to say on the subject.
The News
Shake Rattle and Roll Testing: Jinx 1.2 from Corensic
There is an interesting software test system with very interesting technology and people, that is worth taking a look at IMHO. And today they are announcing JINX 1.2, with the additional of support for AVX among their new features.
I was a little "slow" in figuring out what all the fuss was about when I first met them more than a year ago. They like to play up their product as "testing" your code by making it "unlucky." Makes for cool marketing and a funny product name.
I was a little "slow" in figuring out what all the fuss was about when I first met them more than a year ago. They like to play up their product as "testing" your code by making it "unlucky." Makes for cool marketing and a funny product name.
Intel® ArBB Code Tips
This page contains links to code examples and development tips for building better Intel® ArBB code.
Tips for Debugging Run-time Failures in Intel Fortran Applications
Run-time crashes can be slow and hard to debug. Use compiler options to get more information about such failures before starting time-consuming interactive debugging.
Debugging heavily threaded parallel code
Anyone who has tried to find a problem or make sense of someone else's heavily threaded parallel code knows how cumbersome it can be to identify where a run-time problem really comes from.
