0x00008260 <+64>: ldr r3, [pc, #240] 0x00008264 <+68>: cmp r1, #0 => 0x00008268 <+72>: beq 0x8270 0x0000826c <+76>: mov r3, r1 0x00008270 <+80>: mov sp, r3
(gdb) p/x $r1 $2 = 0xfffef690 But r1 is not zero when using Gdb remote-debug, so it will enter 0x0000826c <+76>: mov r3, r1 QEMU 5.0.0. GNU gdb (GDB; SUSE Linux Enterprise 12) 8.0.1 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1914021 Title: qemu: uncaught target signal 4 (Illegal instruction) but gdb remote- debug exited normally Status in QEMU: New Bug description: I'm getting Illegal instruction (core dumped) when running the attached a.out_err binary in qemu, but when using Gdb to remote-debug the program, it exited normally. will appreciate if you can help look into this qemu issue. readelf -h a.out_err ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: ARM Version: 0x1 Entry point address: 0x8220 Start of program headers: 52 (bytes into file) Start of section headers: 54228 (bytes into file) Flags: 0x5000200, Version5 EABI, soft-float ABI Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 3 Size of section headers: 40 (bytes) Number of section headers: 16 Section header string table index: 15 qemu-arm version 4.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1914021/+subscriptions
