Linux on Power SDK的QEMU环境GDB调试配置求助

Got it, let's work through this GDB debugging issue step by step—since you already got the Hello World binary running via QEMU, we're halfway there. Here are the most common pitfalls and fixes to check:

• Use the correct cross-GDB binary
  Make sure you're not using your system's native GDB—you need the cross-compiler variant from your installed SDK/toolchain, like powerpc64le-linux-gnu-gdb (adjust the target triplet if your setup uses a different variant). Run powerpc64le-linux-gnu-gdb --version to confirm it's tied to your toolchain; mismatched GDB versions will cause architecture compatibility issues.

• Launch QEMU with debug listening enabled
  You need to start QEMU in remote debug mode so GDB can attach. Your launch command should include the -g flag to specify a debug port, like:

  qemu-ppc64le -g 1234 ./hello-world
  

  Without this flag, QEMU won't listen for GDB connections, leading to "connection refused" errors later.

• Connect GDB to QEMU properly
  After starting QEMU, launch your cross-GDB and run these commands to establish the connection:

  powerpc64le-linux-gnu-gdb ./hello-world
  (gdb) target remote localhost:1234
  

  If you get a connection error, verify QEMU is running and listening on the specified port with netstat -tulpn | grep 1234.

• Ensure your binary has debug symbols
  Your Hello World must be compiled with the -g flag to include debug information. Double-check your compile command— it should look like:

  powerpc64le-linux-gnu-gcc -g -o hello-world hello-world.c
  

  You can confirm symbols exist by running powerpc64le-linux-gnu-readelf -S ./hello-world and looking for .debug_* sections. Without these, GDB can't show line numbers or inspect variables.

• Source the SDK environment script
  If you haven't already, source the SDK's setup script to set up correct paths for target sysroots and toolchain binaries. It usually looks like:

  source /path/to/your/sdk/environment-setup-powerpc64le-linux
  

  Skipping this can lead GDB to mislocate target libraries, causing errors like "No such file or directory" during debugging.

• Point QEMU to the target sysroot
  QEMU user-space emulation might try to use your host Ubuntu libraries instead of the SDK's target libraries. Fix this by adding the -L flag to point to your SDK's sysroot:

  qemu-ppc64le -L /path/to/sdk/sysroots/powerpc64le-linux -g 1234 ./hello-world
  

  This ensures QEMU uses the correct libraries matching your cross-compiled binary.

If you run into a specific error message (like memory access issues, library mismatches, or breakpoints not hitting), share that detail and we can narrow it down further!

内容的提问来源于stack exchange，提问作者cbg