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] Implement gdbarch_core_read_description Date: Wed, 09 Aug 2017 14:46:00 -0000 [thread overview] Message-ID: <b1a6c1cea365f80b90c0bca795c8d16fa0681560@gdb-build> (raw) *** TEST RESULTS FOR COMMIT b1a6c1cea365f80b90c0bca795c8d16fa0681560 *** Author: Jiong Wang <jiong.wang@arm.com> Branch: master Commit: b1a6c1cea365f80b90c0bca795c8d16fa0681560 [AArch64] Implement gdbarch_core_read_description Currently, AArch64 only have one target description which is tdesc_aarch64. So, we haven't implemented any target description detection mechanism for core file. This patch is an initial implementation of core_read_description method. Future features can use this to return selected description. gdb/ * aarch64-linux-tdep.c (aarch64_linux_core_read_description): New function. (aarch64_linux_init_abi): Register gdbarch_core_read_description.
next reply other threads:[~2017-08-09 14:46 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-09 14:46 sergiodj+buildbot [this message] 2017-08-09 14:46 ` *** COMPILATION FAILED *** Failures on Fedora-s390x-m64, branch master *** BREAKAGE *** sergiodj+buildbot 2017-08-09 16:35 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-08-09 16:42 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-08-09 17:31 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-08-09 17:37 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-08-09 17:46 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-08-13 20:56 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-08-13 20:59 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-08-13 21:02 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-08-13 21:03 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-08-13 21:37 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-08-13 23:04 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-08-09 17:49 [binutils-gdb] [AArch64] Implement gdbarch_core_read_description 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=b1a6c1cea365f80b90c0bca795c8d16fa0681560@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).