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/gdb-7.12-branch] x32: Fix gdb.trace/mi-trace-frame-collected.exp Date: Wed, 24 Aug 2016 08:29:00 -0000 [thread overview] Message-ID: <644e90fe669bbfe1d15d1018b4fc136af3aab424@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 644e90fe669bbfe1d15d1018b4fc136af3aab424 *** Author: Pedro Alves <palves@redhat.com> Branch: gdb-7.12-branch Commit: 644e90fe669bbfe1d15d1018b4fc136af3aab424 x32: Fix gdb.trace/mi-trace-frame-collected.exp gdb.trace/mi-trace-frame-collected.exp has a couple failures on x32: FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-frame-collected (register) FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-frame-collected (register) gdb.log: -trace-frame-collected ^done,explicit-variables=[{name="gdb_char_test",value="0 '\\000'"}],computed-expressions=[],registers=[{number="16",value="0x4004dc"},{number="204",value="0x4004dc"}],tvars =[],memory=[{address="0x00601060",length="1"}] (gdb) FAIL: gdb.trace/mi-trace-frame-collected.exp: live: -trace-frame-collected (register) [...] -trace-frame-collected ^done,explicit-variables=[{name="gdb_char_test",value="0 '\\000'"}],computed-expressions=[],registers=[{number="16",value="0x4004dc"},{number="204",value="0x4004dc"}],tvars =[],memory=[{address="0x00601060",length="1"}] (gdb) FAIL: gdb.trace/mi-trace-frame-collected.exp: tfile: -trace-frame-collected (register) This test only collects the PC, and thus expects to only see one register in the output of -trace-frame-collected. However, while on the 64-bit ABI gdb only exposes 64-bit $pc/$rip (register 16 above), on x32, GDB exposes 32-bit $eip as well, as a pseudo-register (register 204 above). Thus, collecting $pc/$rip automatically always collects $eip as well. gdb/testsuite/ChangeLog: 2016-08-23 Pedro Alves <palves@redhat.com> * gdb.trace/mi-trace-frame-collected.exp (test_trace_frame_collected): On x32, expect two registers.
next reply other threads:[~2016-08-24 2:18 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-08-24 8:29 sergiodj+buildbot [this message] 2016-08-24 9:12 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.12-branch sergiodj+buildbot 2016-08-24 10:27 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2016-08-24 10:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-08-24 11:26 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-08-24 12:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-08-24 12:42 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2016-08-24 13:23 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-08-24 13:35 ` Failures on Fedora-i686, " sergiodj+buildbot 2016-08-24 13:58 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-08-24 14:12 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2016-08-24 16:06 ` Failures on Debian-i686, " sergiodj+buildbot 2016-08-24 16:23 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2016-08-24 19:31 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-08-24 21:02 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-08-25 3:48 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-08-25 5:29 ` Failures on Fedora-ppc64le-native-gdbserver-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=644e90fe669bbfe1d15d1018b4fc136af3aab424@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).