| commit | 6f3dab758fbcb7814ddfe09fb8224a38f45eb35c | [log] [tgz] |
|---|---|---|
| author | Tom de Vries <tdevries@suse.de> | Sun Mar 30 16:45:25 2025 +0200 |
| committer | Tom de Vries <tdevries@suse.de> | Sun Mar 30 16:45:25 2025 +0200 |
| tree | 30d2bfb9e0079fbdf40862868e9ed8fb5e5796f5 | |
| parent | 79580fac6f582027aa3d51952728e34391c7d6be [diff] |
[gdb/tdep] Fix mmap syscall mapping There are a few spots where an mmap system call is mapped onto enum gdb_syscall value gdb_sys_mmap2. Strictly speaking, this is incorrect. Fix this by mapping to enum gdb_syscall value gdb_old_mmap instead. No functional changes: both gdb_old_mmap and gdb_sys_mmap2 are handled the same in record_linux_system_call. Tested by rebuilding on x86_64-linux.