public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] aarch64-linux process record: more syscalls Date: Mon, 29 Feb 2016 17:29:00 -0000 [thread overview] Message-ID: <d521906965b3e94648a723a13576236aaba301d0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT d521906965b3e94648a723a13576236aaba301d0 *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: d521906965b3e94648a723a13576236aaba301d0 aarch64-linux process record: more syscalls The last patch supports several syscalls in linux-record.c, so now GDB aarch64-linux backend can return these canonicalized syscall numbers per aarch64 syscall number. This patch fixes the following fails, Process record and replay target doesn't support syscall number 59^M Process record: failed to record execution log.^M ^M Program stopped.^M 0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M (gdb) FAIL: gdb.reverse/pipe-reverse.exp: continue to breakpoint: marker2 Process record and replay target doesn't support syscall number 59^M Process record: failed to record execution log.^M ^M Program stopped.^M 0x00000020000eab28 in pipe () from /lib/aarch64-linux-gnu/libc.so.6^M (gdb) FAIL: gdb.reverse/readv-reverse.exp: continue to breakpoint: marker2 gdb: 2016-02-29 Yao Qi <yao.qi@linaro.org> * aarch64-linux-tdep.c (aarch64_canonicalize_syscall): Support eventfd2, eventfd2, dup3, inotify_init1, fallocate and pipe2. Return gdb_sys_epoll_create1 instead of gdb_sys_epoll_create for aarch64_sys_epoll_create1.
next reply other threads:[~2016-02-29 17:29 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-02-29 17:29 sergiodj+buildbot [this message] 2016-02-29 17:30 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot 2016-02-29 17:44 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2016-02-29 17:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-02-29 17:58 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-02-29 18:06 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2016-02-29 18:06 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2016-02-29 18:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2016-02-29 18:34 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-02-29 18:40 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2016-02-29 19:22 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-02-29 19:49 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2016-02-29 19:57 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2016-02-29 20:34 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-02-29 20:43 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-02-29 21:25 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2016-02-29 21:28 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-02-29 21:29 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-02-29 22:04 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-02-29 22:23 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2016-03-01 10:56 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
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=d521906965b3e94648a723a13576236aaba301d0@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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).