https://bugs.kde.org/show_bug.cgi?id=509406
--- Comment #9 from Paul Floyd <[email protected]> --- I've modified vgdb on arm64 to print out the first 10 32bit words from invoker_invoke_gdbserver using ptrace: ^CDEBUG: invoker_invoke_gdbserver 10 32bit words of instructions a9be7bfd f9000bf3 910003fd 529e01a8 72b175a8 6b08001f 54000c61 f0008bf3 b9425a68 350004e8 According to objdump that should be Disassembly of section .text: 0000000000000e48 <vgPlain_invoke_gdbserver>: /* Using ptrace calls, vgdb will force an invocation of gdbserver. VG_(invoke_gdbserver) is the entry point called through the vgdb ptrace technique. */ void VG_(invoke_gdbserver) ( int check ) { e48: a9be7bfd stp x29, x30, [sp, #-32]! e4c: f9000bf3 str x19, [sp, #16] e50: 910003fd mov x29, sp e54: 529e01a8 mov w8, #0xf00d // #61453 e58: 72b175a8 movk w8, #0x8bad, lsl #16 gdbserver. Otherwise, we let the valgrind scheduler invoke gdbserver at the next poll. This poll will be made very soon thanks to a call to VG_(force_vgdb_poll). */ int n_tid, vgdb_interrupted_tid_local = 0; vg_assert (check == 0x8BADF00D); e5c: 6b08001f cmp w0, w8 e60: 54000c61 b.ne fec <vgPlain_invoke_gdbserver+0x1a4> // b.any if (busy) { e64: 90000013 adrp x19, 0 <vgPlain_ppPointKind> e68: b9400268 ldr w8, [x19] e6c: 350004e8 cbnz w8, f08 <vgPlain_invoke_gdbserver+0xc0> That's not quite the same, the two words after the addert are different. -- You are receiving this mail because: You are watching all bug changes.
