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] Add several "quit with live inferior" tests Date: Tue, 17 Oct 2017 17:30:00 -0000 [thread overview] Message-ID: <8484c9554519c25c73a349d0581cc269f102c5d2@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 8484c9554519c25c73a349d0581cc269f102c5d2 *** Author: Pedro Alves <palves@redhat.com> Branch: master Commit: 8484c9554519c25c73a349d0581cc269f102c5d2 Add several "quit with live inferior" tests In my multi-target branch, I had managed to break GDB exiting successfuly in response to "quit" or SIGHUP/SIGTERM when: - you're debugging with "target extended-remote", - have more than one inferior loaded in gdb, some running, and at least one not running, and, - quit gdb with the inferior that is not running yet selected. The testsuite still passed cleanly anyway. I only noticed because I was left with a bunch of core dumps in the gdb/testsuite/ directory -- the testsuite infrastructure closes GDB's pty after running each testcase, which results in GDB getting a SIGHUP and should make GDB exit gracefully. If GDB crashes at that point though, there's no indication about it in gdb.sum/gdb.log. This commit adds a multitude of tests exercising quitting GDB with live inferiors, some of which would have caught the problem. gdb/testsuite/ChangeLog: 2017-10-17 Pedro Alves <palves@redhat.com> * gdb.base/quit-live.c: New file. * gdb.base/quit-live.exp: New file.
next reply other threads:[~2017-10-17 17:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-17 17:30 sergiodj+buildbot [this message] 2017-10-17 17:30 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-10-17 22:06 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-10-17 22:36 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-10-17 23:14 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-10-17 23:38 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-18 0:02 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2017-10-20 1:01 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-10-20 3:07 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-10-20 3:25 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-10-20 3:49 ` Failures on Fedora-x86_64-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=8484c9554519c25c73a349d0581cc269f102c5d2@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).