Let's break down the problems you're facing and walk through practical fixes, based on common pitfalls with LEON3/QEMU setups:

1. Fix Undefined Behavior & Output Buffering #

Your code has two critical issues that cause unpredictable behavior:

• Uninitialized variables: a, b, c, d, e are automatic variables with no initial values—stack memory on LEON3 will have random garbage here, so those if branches might execute unexpectedly, leading to crashes or weird program flow.
• Unflushed output: Standard output is line-buffered by default. Without a newline or explicit flush, your printf message won't show up in QEMU's nographic mode.

Update your code like this:

#include <stdio.h>
#include <stdint.h>
int main(void) {
    int a=0, b=0, c=0, d=0, e=0; // Initialize variables to avoid undefined behavior
    printf("hello world!\n"); // Add newline to trigger output flush
    // Alternatively, use fflush(stdout); if you don't want a newline
    if(a){ a++; };
    if(b){ b++; };
    if(c){ c++; };
    if(d){ d++; };
    if(e){ e++; };
    while(1){ }
    return 0;
}

2. Use the Correct Cross-Compiler #

LEON3 is a SPARC-based processor—you can't use your host system's GCC to compile code for it. You need a SPARC cross-toolchain (like sparc-elf-gcc or sparc-linux-gnu-gcc):

• Compile your code with this command to ensure compatibility:

sparc-elf-gcc -msoft-float -static -o testapp.elf testapp.c

• -static: Bundles all dependencies into the ELF (QEMU's LEON3 emulation doesn't include a dynamic linker or system libraries by default)
• -msoft-float: Disables hardware floating-point (most LEON3 configurations lack an FPU; omitting this will cause immediate crashes)

3. Validate ELF & QEMU Command Line #

• Check ELF architecture: Run sparc-elf-readelf -h testapp.elf to confirm the machine type is SPARC or SPARC32PLUS. If it shows your host architecture (e.g., x86_64), QEMU can't execute it and will exit immediately.
• Enable debug logs: Add -d guest_errors to your QEMU command to get detailed crash/error messages:

qemu-system-sparc.exe -nographic -M leon3_generic -m 64M -kernel testapp.elf -d guest_errors

4. Fix GDB Debugging Errors #

The QEMU: Terminated via GDBstub error usually happens when GDB sends a terminate signal (e.g., if you run quit in GDB while connected). To properly debug your program:

1. Start QEMU in debug mode, paused at the entry point:

qemu-system-sparc.exe -nographic -M leon3_generic -m 64M -kernel testapp.elf -s -S

2. Open your cross-GDB in a separate terminal:

sparc-elf-gdb testapp.elf

3. Connect to QEMU's debug stub:

target remote localhost:1234

4. Now you can set breakpoints (e.g., break main) and step through code with continue, step, etc.

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