diff options
| author | Tom de Vries <tdevries@suse.de> | 2024-11-13 19:37:04 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2024-11-13 19:37:04 +0100 |
| commit | 76b9b6eb9c76400c3419606ca5d0d4f1cec45536 (patch) | |
| tree | f4a55175069b4ffea818240c6cf7d92d45b55064 /gdb/linux-tdep.c | |
| parent | 5d9887ffa2628ef93bc3cddd58e6c374b2a16ca7 (diff) | |
| download | binutils-76b9b6eb9c76400c3419606ca5d0d4f1cec45536.zip binutils-76b9b6eb9c76400c3419606ca5d0d4f1cec45536.tar.gz binutils-76b9b6eb9c76400c3419606ca5d0d4f1cec45536.tar.bz2 | |
[gdb/tdep] Handle sycall statx for arm-linux
When running test-case gdb.reverse/fstatat-reverse.exp on arm-linux, I run
into:
...
(gdb) continue^M
Continuing.^M
Process record and replay target doesn't support syscall number 397^M
Process record does not support instruction 0xdf00 at address 0xf7ebf774.^M
Process record: failed to record execution log.^M
^M
Program stopped.^M
0xf7ebf774 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6^M
(gdb) FAIL: gdb.reverse/fstatat-reverse.exp: continue to breakpoint: marker2
...
Syscall number 397 stands for statx on arm-linux.
Fix this by handling 397 in arm_canonicalize_syscall.
Tested on arm-linux.
Reviewed-By: Guinevere Larsen <guinevere@redhat.com>
Approved-By: Luis Machado <luis.machado@arm.com>
Diffstat (limited to 'gdb/linux-tdep.c')
0 files changed, 0 insertions, 0 deletions