Hi every one, i create a program in qt and this program working well in my desktop environment, but when i run this program on mini6410 sometimes don't load and get segmentation fault, sometimes load and when i test touch smashing get segmentation fault, sometimes after two hour get gcc cant allocate, sometimes work good, so how can i debug my program on mini6410? can i debug with qt creator? i see a arm-linux-gdb in toolchain to how can i use that? tnx a lot;
Debug qt
> i see a arm-linux-gdb in toolchain to how can i use that? Google for "cross debugging" or "remote debugging"
but arm-linux-gdb don't support remote debugging and i haven't a gdbserver for mini6410, may be i can compile this tools, but no body debug his program on mini6410 before?
> but no body debug his program on mini6410 before? Sure. It is very simple if you have a powerful development environment where you have the full control over the target's root filesystem. So, I would suggest you first start to build your own Mini6410 root filesystem, where *you* decide what to build and how. Then you can add your own application on top of it.
Ok so i think maybe you must go farther and say something help me really. what version of gdb must i compile and others test, using openssh is better or not, some manuals for debugging on mini devices, something really help me?
> Ok so i think maybe you must go further and say > something help me really. > what version of gdb must i compile and others test, [...] Not only single packages. The whole root filesystem must be under your control. There are various buildsystems for embedded targets around and also binary distributions like embedian. At least the buildsystems gives you a reliable way to get a reproducible root filesystem your own application can rely on (and run on, without strange failures). First of all, you must ensure the libs and headers your Qt application is cross compiled and linked to (on your host) are the same that exist on your target. If not, many funny things will happen...