diff options
author | Tom de Vries <tdevries@suse.de> | 2024-11-13 22:41:35 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2024-11-13 22:41:35 +0100 |
commit | 580f291cb804c65d9bcbdd0e618233f8bee0c2ff (patch) | |
tree | 8e9e08e682f6022ff5ccc08289b700a3cac4be54 /config/lthostflags.m4 | |
parent | 5cb0406bb64da200520ab3a9ee8f2a3c58ea6be0 (diff) | |
download | gdb-master.zip gdb-master.tar.gz gdb-master.tar.bz2 |
When running test-case gdb.reverse/time-reverse.exp on arm-linux, I run into:
...
(gdb) continue^M
Continuing.^M
Process record and replay target doesn't support syscall number 403^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: $exp: mode=c: continue to breakpoint: marker2
...
Syscall number 403 stands for clock_gettime64 on arm-linux.
Fix this by handling 403 in arm_canonicalize_syscall, and handling
gdb_sys_clock_gettime64 elsewhere.
Since i386_canonicalize_syscall is the identity function, enum value
gdb_sys_clock_gettime64 gets a value to match i386, which also happens to be
403.
Tested on arm-linux.
Approved-By: Guinevere Larsen <guinevere@redhat.com> (record-full)
Diffstat (limited to 'config/lthostflags.m4')
0 files changed, 0 insertions, 0 deletions