Gdbserver support arm trace point

Question

I compiled gdbserver 7.6 for a hand with:

cd /gdb-7.6-src/gdb/gdbserver ./configure --target=arm-linux --host=arm-linux make CC=/path/to/cross-compiler-gcc 

Then I compiled gdb 7.6 for a hand with:

 cd /gdb-7.6-src/ ./configure --target=arm-linux --prefix=/opt/gdb-arm/install/ make && make install 

I compiled my trivial application:

 /path/to/cross-compiler-gcc hello.c -g -o hello 

I copied gdbserver and my cross-compiled application on my board. From my computer (x86-pc-linux) I run:

 gdb hello (gdb) set target-async on (gdb) tvariable $c (gdb) actions >teval $c=$c+1 >end (gdb) break main (gdb) target remote <ipaddr>:<port> [Thread 1585] #1 stopped. 0x40000800 in ?? () Cannot access memory at address 0x0 (gdb) continue & (gdb) tstart Target does not support this command. (gdb) tstatus Target does not support this command. 

The behavior is "normal" before the tstart command: I can debug the application the way I want, but I can not start tracking the application.

Question: Does gdbserver support trace points for the hand or only for x86 / amd_64?

Answer 1

I was looking for something that I found in online documents of online GDB documents that now there is no support for any Archs.

Check additional information: https://sourceware.org/gdb/onlinedocs/gdb/Tracepoints.html

Citation:

This functionality is implemented in a remote stub; however, none of the stubs allocated by the GDB tracking points since this entry