Comment 1 for bug 1901966

This doesn't seem to be related to the previous bugs.

I tried to reproduce this on 18.04.4 (I don't have 20.04) and a fresh build of GDB master, and I couldn't.

(gdb) disass _start
Dump of assembler code for function _start:
   0x00010074 <+0>: mov r7, #4
   0x00010078 <+4>: mov r0, #1
   0x0001007c <+8>: ldr r1, [pc, #12] ; 0x10090 <_start+28>
   0x00010080 <+12>: ldr r2, [pc, #12] ; 0x10094 <_start+32>
   0x00010084 <+16>: svc 0x00000000
   0x00010088 <+20>: mov r7, #1
   0x0001008c <+24>: svc 0x00000000
   0x00010090 <+28>: muleq r2, r8, r0
   0x00010094 <+32>: andeq r0, r0, lr
End of assembler dump.
(gdb) b _start
Breakpoint 1 at 0x10074: file /tmp/hello.S, line 4.
(gdb) r
Starting program: /tmp/hello

Breakpoint 1, _start () at /tmp/hello.S:4
4 MOV R7, #4

With Ubuntu 18.04.4's GDB it also works.

Can you please turn on debugging and paste the log?

Use "set debug infrun 1" before the run command.