This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Remote Debugging MontaVista Application Examples program ./encode

Expert 1130 points

I'm trying to debug the ./encode program, but I can't seem to get the remote debugging to work. Page 58 of the MontaVista Linux Professional Edition 4.0 Application Developers Guide (Document Release Date January 6, 2006) gives instructions on how to do remote debugging using gdbserver and ddd. The instructions uses the command

>ddd --debugger 586-gdb --gdb ./encode

This does not work because gdb doesn't startup. I have to change the command to

>ddd --debugger gdb --gdb ./encode

This seems to work the prompt on the target changes from "Listening on port 1000" to "Remote debuggin from host 10.8.105.18" DDD does startup, but there's no source code displayed. I figured this was because the code was not compiled with a debug option so I ran >make debug in the dvsdk_1_30_01_41 directory which seems to work, but I get an error when I do a >make install

What's the best way to debug a Monta Vista application?

  • I recommend you to read Running Demo via ddd on DVEVM ,  Juan explains the details in this document.

  • I've reviewed the app note. I have a debug directory with object files and no executables. How do build the encode app with debug info?

    Mike

  • I was able to start DDD and set a breakppoint and select CONT and then NEXT, but gdb gets hung.

     

    Mike

  • Do you get any error messages or warnings out of DDD? I have run through Juan's application note before and was able to get DDD to step through and function properly, and I know others have gotten it to work with his steps so I would suspect something specific about your host setup.

    I find DDD to be rather tedious to setup and use (though it has been stable when I use it), so for most simple debugging I try to avoid using DDD and just use many print statements (seems old fashioned after using tools like CCS but it works). If you are looking for a more robust integrated development environment than you may want to consider purchasing a full version of Monta Vista which includes the DevRocket IDE, it is Eclipse based and will likely do a better job for you than DDD.

  • Hi Mike,

      I encountered the same problem with you said.  If you just debug ARM application (I mean this application do not call codec engine in DSP side ) using DDD, I think it should not have any problems.  When I debug my code, this problem usully occurs when I use DDD to debug ARM while debugging Codec using CCS.  If my codec has some errors, CCS can respond properly, but DDD can not go next any more, it will not respond, so I wonder whether your codec has some problems.