Remote Debugging for ARM - signal SIGILL

Hi,
I am trying to remote debug an application using ddd on a ARM device running "Linux beagleboard 2.6.32 #1 PREEMPT Thu Apr 15 12:05:47 CEST 2010 armv7l GNU/Linux"

I configured ddd to connect to the gdbserver on the beagleboard:

(gdb) target remote 192.168.0.1:2345

0x400007f0 in _dl_start_user () from /sourcery_root/lib/ld-linux.so.3
(gdb) target remote 192.168.0.1:2345
192.168.0.1:2345: Connection timed out.
(gdb) target remote 192.168.0.1:2345
0x400007f0 in _dl_start_user () from /sourcery_root/lib/ld-linux.so.3
(gdb) c

Program received signal SIGILL, Illegal instruction.
0x40045524 in ?? ()
(gdb) bt
#0  0x40045524 in ?? ()
#1  0x40025050 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

Could someone give a hint where to look at?
Regards,
Chris

(gdb) target remote 192.168.0.1:2345
0x400007f0 in _dl_start_user () from /sourcery_root/lib/ld-linux.so.3

After this,
(gdb) b main

Then go step by step
gdb ) s

in gdb, you should set the syspath before command continue.
It looks like that you are using the Sourcery G++ Lite cross tool-chain?

In its manual of gdb, a section "Setting the Sysroot in the Debugger" should be read.

(gdb) set sysroot-on-target target-pathname
(gdb) set sysroot host-pathnam

Then, ?? () may be disappeared.

Hope it be helpful.

Originally Posted by chrisARM Hi, I am trying to remote debug an application using ddd on a ARM device running "Linux beagleboard 2.6.32 #1 PREEMPT Thu Apr 15 12:05:47 CEST 2010 armv7l GNU/Linux" I configured ddd to connect to the gdbserver on the beagleboard: (gdb) target remote 192.168.0.1:2345 0x400007f0 in _dl_start_user () from /sourcery_root/lib/ld-linux.so.3 (gdb) target remote 192.168.0.1:2345 192.168.0.1:2345: Connection timed out. (gdb) target remote 192.168.0.1:2345 0x400007f0 in _dl_start_user () from /sourcery_root/lib/ld-linux.so.3 (gdb) c Program received signal SIGILL, Illegal instruction. 0x40045524 in ?? () (gdb) bt #0 0x40045524 in ?? () #1 0x40025050 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) Could someone give a hint where to look at? Regards, Chris

compile the c++ source files with -march=armv4

In build/core/combo/arm/yourarch.mk put -march=armv4 and then do mm -B showcommands to check if it was used.

Then gdbserver can handle it.