How to single step ARM assembly in GDB on QEMU?

by

Your problem here is that you’re trying to run an ARM gdb under QEMU’s user-mode emulation. QEMU doesn’t support the ptrace syscall (that’s what syscall number 26 is), so this is never going to work.

What you need to do is run your test binary under QEMU with the QEMU options to enable QEMU’s own builtin gdb stub which will listen on a TCP port. Then you can run a gdb compiled to run on your host system but with support for ARM targets, and tell that to connect to the TCP port.

(Emulating ptrace within QEMU is technically very tricky, and it would not provide much extra functionality that you can’t already achieve via the QEMU builtin gdbstub. It’s very unlikely it’ll ever be implemented.)

More Related Contents:

  1. How to debug the Linux kernel with GDB and QEMU?
  2. Using gdb to single-step assembly code outside specified executable causes error “cannot find bounds of current function”
  3. Running 32 bit assembly code on a 64 bit Linux & 64 bit Processor : Explain the anomaly
  4. ARM inline asm: exit system call with value read from memory
  5. Initial state of program registers and stack on Linux ARM
  6. What are the calling conventions for UNIX & Linux system calls (and user-space functions) on i386 and x86-64
  7. glibc scanf Segmentation faults when called from a function that doesn’t align RSP
  8. Is there a way to change the environment variables of another process in Unix?
  9. Nasm segmentation fault on RET in _start
  10. How to print a number in assembly NASM?
  11. Hello, world in assembly language with Linux system calls?
  12. How to disassemble 16-bit x86 boot sector code in GDB with “x/i $pc”? It gets treated as 32-bit
  13. How to add a new device in QEMU source code?
  14. Why data and stack segments are executable?
  15. How to print a character in Linux x86 NASM?
  16. Core dump file is not generated
  17. Number of executed Instructions different for Hello World program Nasm Assembly and C
  18. How to use debug version of libc
  19. Trying to understand gcc’s complicated stack-alignment at the top of main that copies the return address
  20. Segmentation fault on printf – NASM 64bit Linux
  21. GDB: Listing all mapped memory regions for a crashed process
  22. Do Kernel pages get swapped out?
  23. How can I do memory test on Arm architecture hardware? (something like Memtest86) [closed]
  24. Why do we need a bootloader in an embedded device?
  25. How to print exact value of the program counter in C
  26. Linux x64: why does r10 come before r8 and r9 in syscalls?
  27. Writing a putchar in Assembly for x86_64 with 64 bit Linux?
  28. Disable AVX-optimized functions in glibc (LD_HWCAP_MASK, /etc/ld.so.nohwcap) for valgrind & gdb record
  29. Responsibility of stack alignment in 32-bit x86 assembly
  30. Write system call won’t print characters from a register

Leave a Comment