When writing programs, ideally spoken you should think hard enough and your code should be "first time right". But as I said, ideally spoken...
Reality is in (can I say) 100% of the cases different: one simply needs at some moment(s) in time a debugger.
For the FoxBoard, that's not so obvious. Ok, I know, there's GDB and you can activate gdbdebugger on the FoxBoard, but still, debugging on the GDB command line is only for the "happy few"...
I myself prefer to have something more graphical.
I've searched quite a bit to find what I was looking for. I've used Eclipse, NetBeans, KDevelop and other exotic applications, but none of them could convince me to used it together with the FoxBoard to debug.
I then found DDD, a graphical debugger that can be connected to the FoxBoard. This one is good, very good even. For those interested, I wrote an article on my Wiki website, which can be read here.
But I was still looking for something more "intuitive", something which looks more to the (sorry Linux guys) Windows debuggers, like there are Visual Studio/Visual Express (why always taking Micro$oft as a reference???). Am I spoiled? Yes, for sure, I am spoiled. At least regarding debug environments...
I finally found Insight, a debugger GUI made by RedHat. This looks very much to what I am used to see on Windows environments.
However, like DDD, Insight is not "right out of the box" useable. The reason is that this debugger is very "versatile": a lot of targets are supported, among them the CRIS one!
You have to download the sources and compile it yourself. But don't worry, I also wrote an article on how to do this on my Wiki pages.
As usual, for the ones interested, they can read the article here.
Overall, I'm quite satisfied about this debugger. Of course, this one too has its advantages and disadvantages, but on a scale of 10, I would give it a 7.
For sure, better than all the rest I've looked into.
Have fun reading the article, building the debugger and applying it on the FoxBoard!
No comments:
Post a Comment