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] Enable gdb.base/inferior-died.exp on is_remote target boards Date: Thu, 12 Oct 2017 18:10:00 -0000 [thread overview] Message-ID: <4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f Enable gdb.base/inferior-died.exp on is_remote target boards We support follow-fork in the remote protocol nowadays. Also, the right way to enable non-stop mode is to do it before connecting, and for use_gdb_stub boards, that means we have to do it at gdb_load time. The "modern" pattern for that is to pass non-stop in GDBFLAGS. This makes the test pass with --target_board=native-gdbserver. gdb/testsuite/ChangeLog: 2017-10-12 Pedro Alves <palves@redhat.com> Simon Marchi <simon.marchi@polymtl.ca> * gdb.base/inferior-died.exp: Remove is_remote and isnative checks. Use build_executable + clean_restart instead of prepare_for_testing. Pass "set non-stop on" via GDBFLAGS instead of enabling non-stop after starting gdb.
next reply other threads:[~2017-10-12 18:10 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-12 18:10 sergiodj+buildbot [this message] 2017-10-12 18:10 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-10-12 18:48 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-12 18:55 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-10-12 19:16 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-10-12 19:21 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-12 19:47 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-12 20:19 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2017-10-12 20:28 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-12 20:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-10-12 21:04 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-10-12 21:35 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-10-12 23:14 ` 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=4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f@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).