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] Make gdb.base/auvx.exp work with --target_board=native-extended-gdbserver Date: Fri, 13 Oct 2017 02:40:00 -0000 [thread overview] Message-ID: <9192b7decc7256a41502bf68df36f429cceffc89@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 9192b7decc7256a41502bf68df36f429cceffc89 *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 9192b7decc7256a41502bf68df36f429cceffc89 Make gdb.base/auvx.exp work with --target_board=native-extended-gdbserver Currently we get: Running .../src/gdb/testsuite/gdb.base/auxv.exp ... WARNING: can't generate a core file - core tests suppressed - check ulimit -c After this commit we get all the same PASSes as when native testing. The problem is that the testcase wants to create a core dump in a temporary directory and it is using the "cd" command to start the inferior with that directory as current directory, but that command only affects the inferior's cwd when native debugging. Fix it by using using the new "set cwd" command instead, which works with gdbserver as well. This still won't work with stub-like targets, because with those when we connect the inferior is already running. It'd be possible to make it work by making the inferior itself change dirs, but we'll need to make the native-gdbserver board no longer set is_remote first. gdb/testsuite/ChangeLog: 2017-10-12 Pedro Alves <palves@redhat.com> * gdb.base/auvx.exp (coredir): Update comment. (top level) <core_works>: Use "set cwd" command instead of "cd" command.
next reply other threads:[~2017-10-13 2:40 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-13 2:40 sergiodj+buildbot [this message] 2017-10-13 2:40 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-10-13 6:40 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-10-13 7:04 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-13 18:59 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-13 19:18 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-13 19:22 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-10-13 19:39 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-10-13 19:50 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-10-13 19:55 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-10-13 20:08 ` Failures on Fedora-x86_64-native-extended-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=9192b7decc7256a41502bf68df36f429cceffc89@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).