public inbox for
help / color / mirror / Atom feed
From: Tom de Vries <>
Subject: [binutils-gdb] [gdb/tdep] Support catch syscall pipe2 for i386
Date: Mon,  9 May 2022 10:22:05 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=4dcb932e645bdb0e63cecffb626d0805d9a19c27

commit 4dcb932e645bdb0e63cecffb626d0805d9a19c27
Author: Tom de Vries <>
Date:   Mon May 9 12:22:02 2022 +0200

    [gdb/tdep] Support catch syscall pipe2 for i386
    With test-case gdb.base/catch-syscall.exp and target board unix/-m32, we run
    (gdb) catch syscall pipe2^M
    Unknown syscall name 'pipe2'.^M
    (gdb) FAIL: gdb.base/catch-syscall.exp: determine pipe syscall: catch syscall pipe2
    Fix this by:
    - adding a pipe2 entry in gdb/syscalls/, and
    - regenerating gdb/syscalls/i386-linux.xml using
      "xsltproc --output i386-linux.xml apply-defaults.xsl".
    Tested on x86_64-linux with native and unix/-m32.

 gdb/syscalls/i386-linux.xml    | 1 +
 gdb/syscalls/ | 1 +
 2 files changed, 2 insertions(+)

diff --git a/gdb/syscalls/i386-linux.xml b/gdb/syscalls/i386-linux.xml
index a783dd10af3..4a7a2345186 100644
--- a/gdb/syscalls/i386-linux.xml
+++ b/gdb/syscalls/i386-linux.xml
@@ -334,4 +334,5 @@
   <syscall name="eventfd" number="323" groups="descriptor"/>
   <syscall name="fallocate" number="324" groups="descriptor"/>
   <syscall name="timerfd_settime" number="325" groups="descriptor"/>
+  <syscall name="pipe2" number="331" groups="descriptor"/>
diff --git a/gdb/syscalls/ b/gdb/syscalls/
index e778ab54043..13c4d1d99d4 100644
--- a/gdb/syscalls/
+++ b/gdb/syscalls/
@@ -337,4 +337,5 @@
   <syscall name="eventfd" number="323"/>
   <syscall name="fallocate" number="324"/>
   <syscall name="timerfd_settime" number="325"/>
+  <syscall name="pipe2" number="331"/>

                 reply	other threads:[~2022-05-09 10:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

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

  git send-email \ \ \ \

* 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).