Programming

What function would running it on your local machine serve? They're probably not even the same architecture. "file not found" can sometimes, and bafflingly, mean "incorrect architecture". You can't run or debug ARM executables on an x86 machine. This is what you have to do. I don't see why it wouldn't be possible, the robot you're using is a linux machine at core. You might end up needing to build it yourself in your ARM cross-compiler.

@Corona688:

I tried to install gdb on my robot but it has total of 12 MB hard drive whereas, gdb needs atleast 15MB.

So it is giving me "not enough space" error. So i guess would need to debug only with the printf statements

By 'gdb needs 15 megabytes' do you mean 'the source tarball is 15 megabytes'? You don't need to copy over the whole source tarball. Build it on your PC system with your cross compiler and copy over only the executable, and the files it needs to run.

Or if there's some harebrained binary package available that somehow wastes 15 megs of space, extract it manually on your PC and copy over only the minimum things it needs to run. The gdb executable on my system is 3.4 megs in size, and the things it needs under /usr/share/gdb/syscalls/ only a few kilobytes in size.

If you end up printf-ing, try 'fprintf(stderr, "string%d", 4); instead of plain printf, printing to stderr will ensure that it prints unbuffered, i.e. printf("the result is: "); code_that_crashes; ...will probably print nothing, while fprintf(stderr, "the result is: "); code_that_crashes; will print "the result is:" before crashing.

@Corona688:not sure how to copy the executables to the robot.....bt. tried fprintf and definitely it's lotttt better than printf.

Thank you so much, it helped a lott!!!!!