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] S/390: Fix Elf note swap s390_gs_bc vs. s390_gs_cb Date: Thu, 21 Sep 2017 16:21:00 -0000 [thread overview] Message-ID: <8fe09d7421db51bc13c9228547d63e6315bd6bd0@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 8fe09d7421db51bc13c9228547d63e6315bd6bd0 *** Author: Andreas Arnez <arnez@linux.vnet.ibm.com> Branch: master Commit: 8fe09d7421db51bc13c9228547d63e6315bd6bd0 S/390: Fix Elf note swap s390_gs_bc vs. s390_gs_cb Fix two typos that resulted in swapping the BFD names for the core note register sections NT_S390_GS_CB and NT_S390_GS_BC. bfd/ChangeLog: * elf.c (elfcore_grok_note): For the cases NT_S390_GS_CB and NT_S390_GS_BC, correct the previously swapped invocations of elfcore_grok_s390_gs_bc and elfcore_grok_s390_gs_cb.
next reply other threads:[~2017-09-21 16:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-21 16:21 sergiodj+buildbot [this message] 2017-09-21 16:22 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2017-09-21 16:28 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-09-21 16:28 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-21 16:29 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-09-21 16:35 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-09-21 16:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-21 16:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-21 16:40 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-09-21 16:54 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-09-21 17:20 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-21 18:33 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " 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=8fe09d7421db51bc13c9228547d63e6315bd6bd0@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).