public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: gdb-patches@sourceware.org
Subject: [PATCH v1 1/7] gdb: syscalls: Update linux-defaults.xml.in
Date: Thu, 29 Feb 2024 16:39:04 +0800	[thread overview]
Message-ID: <20240229083910.9991-2-yangtiezhu@loongson.cn> (raw)
In-Reply-To: <20240229083910.9991-1-yangtiezhu@loongson.cn>

Make use of the script update-linux-defaults.sh to regenerate the Linux
syscall group info against strace git commit 8c480270653d which will be
released in v6.8.

Like this:

  $ git clone https://github.com/strace/strace.git strace.git
  $ git clone https://sourceware.org/git/binutils-gdb.git gdb.git
  $ cd gdb.git/gdb/syscalls/
  $ ./update-linux-defaults.sh ~/strace.git/

Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
---
 gdb/syscalls/linux-defaults.xml.in | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gdb/syscalls/linux-defaults.xml.in b/gdb/syscalls/linux-defaults.xml.in
index 85b7fff79be..6f6624cb01e 100644
--- a/gdb/syscalls/linux-defaults.xml.in
+++ b/gdb/syscalls/linux-defaults.xml.in
@@ -34,6 +34,7 @@
   <syscall name="bsd43_statfs" groups="file"/>
   <syscall name="bsd43_stat" groups="file"/>
   <syscall name="cacheflush" groups="memory"/>
+  <syscall name="cachestat" groups="descriptor"/>
   <syscall name="chdir" groups="file"/>
   <syscall name="chmod" groups="file"/>
   <syscall name="chown32" groups="file"/>
@@ -70,6 +71,7 @@
   <syscall name="fanotify_init" groups="descriptor"/>
   <syscall name="fanotify_mark" groups="descriptor,file"/>
   <syscall name="fchdir" groups="descriptor"/>
+  <syscall name="fchmodat2" groups="descriptor,file"/>
   <syscall name="fchmodat" groups="descriptor,file"/>
   <syscall name="fchmod" groups="descriptor"/>
   <syscall name="fchown32" groups="descriptor"/>
@@ -138,6 +140,7 @@
   <syscall name="lstat64" groups="file"/>
   <syscall name="lstat" groups="file"/>
   <syscall name="madvise" groups="memory"/>
+  <syscall name="map_shadow_stack" groups="memory"/>
   <syscall name="mbind" groups="memory"/>
   <syscall name="memfd_create" groups="descriptor"/>
   <syscall name="memfd_secret" groups="descriptor"/>
-- 
2.42.0


  reply	other threads:[~2024-02-29  8:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  8:39 [PATCH v1 0/7] gdb: Modify some code about syscalls XML Tiezhu Yang
2024-02-29  8:39 ` Tiezhu Yang [this message]
2024-02-29  8:39 ` [PATCH v1 2/7] gdb: syscalls: Update .xml.in files for some archs Tiezhu Yang
2024-02-29  8:39 ` [PATCH v1 3/7] gdb: syscalls: Update .xml " Tiezhu Yang
2024-02-29  8:39 ` [PATCH v1 4/7] gdb: syscalls: Add loongarch-linux.xml.in Tiezhu Yang
2024-03-20 20:51   ` Pedro Alves
2024-03-21  2:02     ` Tiezhu Yang
2024-02-29  8:39 ` [PATCH v1 5/7] gdb: syscalls: Generate loongarch-linux.xml Tiezhu Yang
2024-02-29  8:39 ` [PATCH v1 6/7] gdb: syscalls: Add loongarch case in update-linux-from-src.sh Tiezhu Yang
2024-02-29  8:39 ` [PATCH v1 7/7] gdb: LoongArch: Set the correct XML syscall filename Tiezhu Yang
2024-03-13  1:18 ` [PING] [PATCH v1 0/7] gdb: Modify some code about syscalls XML Tiezhu Yang
2024-03-18  9:27 ` Tiezhu Yang
2024-03-19 16:29   ` [PING] " John Baldwin
2024-03-20 10:53     ` Tiezhu Yang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240229083910.9991-2-yangtiezhu@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).