public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb/gdb-7.10-branch] PR record/18691: Fix fails in solib-precsave.exp Date: Tue, 18 Aug 2015 14:03:00 -0000 [thread overview] Message-ID: <37419df723ec96b600030970e0fe97aaa82fa2e1@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 37419df723ec96b600030970e0fe97aaa82fa2e1 *** Author: Yao Qi <yao.qi@linaro.org> Branch: gdb-7.10-branch Commit: 37419df723ec96b600030970e0fe97aaa82fa2e1 PR record/18691: Fix fails in solib-precsave.exp We see the following regressions in testing on x86_64-linux, reverse-step^M Cannot access memory at address 0x2aaaaaed26c0^M (gdb) FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function one when GDB reverse step into a function, GDB wants to skip prologue so it requests TARGET_OBJECT_CODE_MEMORY to read some code memory in memory_xfer_partial_1. However in dcache_read_memory_partial, the object becomes TARGET_OBJECT_MEMORY return ops->to_xfer_partial (ops, TARGET_OBJECT_MEMORY, NULL, myaddr, NULL, memaddr, len, xfered_len); in reverse debugging, ops->to_xfer_partial is record_full_core_xfer_partial and it will return TARGET_XFER_E_IO because it can't find any records. The test fails. At this moment, the delegate relationship is like dcache -> record-core -> core -> exec and we want to GDB read memory across targets, which means if the requested memory isn't found in record-core, GDB can read memory from core, and exec even further if needed. I find raw_memory_xfer_partial is exactly what I want. gdb: 2015-08-18 Yao Qi <yao.qi@linaro.org> PR record/18691 * dcache.c (dcache_read_memory_partial): Call raw_memory_xfer_partial. * target.c (raw_memory_xfer_partial): Make it non-static. * target.h (raw_memory_xfer_partial): Declare.
next reply other threads:[~2015-08-18 14:03 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-18 14:03 sergiodj+buildbot [this message] 2015-08-18 14:03 ` Failures on RHEL-s390x-m64, branch gdb-7.10-branch sergiodj+buildbot 2015-08-18 14:49 ` Failures on Fedora-i686, " sergiodj+buildbot 2015-08-18 15:01 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot 2015-08-18 15:04 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2015-08-18 15:07 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-08-18 15:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-08-18 15:11 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-08-18 15:18 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2015-08-18 15:21 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2015-08-18 15:27 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2015-08-18 15:50 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2015-08-18 18:27 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2015-08-18 18:47 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2015-08-18 19:03 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2015-08-18 19:24 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-08-18 19:30 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2015-08-18 19:48 ` Failures on Debian-i686, " sergiodj+buildbot 2015-08-18 20:01 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-08-18 20:06 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-08-18 20:16 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2015-08-18 20:42 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2015-08-18 20:52 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-08-18 21:02 ` 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=37419df723ec96b600030970e0fe97aaa82fa2e1@gdb-build \ --to=sergiodj+buildbot@redhat.com \ --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).