public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "kelly at 219design dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/27125] unwanted interaction of [-ex "bt"] with [-batch -return-child-result]. used to work in gdb 8.1 Date: Tue, 29 Dec 2020 04:56:14 +0000 [thread overview] Message-ID: <bug-27125-4717-r1Wioyi9qW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27125-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27125 --- Comment #1 from kelly at 219design dot com --- I have located the commit that introduced the behavior change. I can clearly see that the change was intentional, and yet I would still like to question whether "-return-child-result" should be given special consideration. Commit that introduced the unexpected "-return-child-result" outcome: commit b0f492b90f3d13da8ac80437e6ecb9a87db4a75b (refs/bisect/bad) Author: Gary Benson <gbenson@redhat.com> Date: Wed Aug 29 16:11:50 2018 +0100 Indicate batch mode failures by exiting with nonzero status This commit causes GDB in batch mode to exit with nonzero status if the last command to be executed fails. gdb/ChangeLog: PR gdb/13000: * gdb/main.c (captured_main_1): Exit with nonzero status in batch mode if the last command to be executed failed. * NEWS: Mention the above. gdb/testsuite/ChangeLog: PR gdb/13000: * gdb.base/batch-exit-status.exp: New file. * gdb.base/batch-exit-status.good-commands: Likewise. * gdb.base/batch-exit-status.bad-commands: Likewise. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-29 4:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-29 1:22 [Bug cli/27125] New: " kelly at 219design dot com 2020-12-29 4:56 ` kelly at 219design dot com [this message] 2020-12-29 4:58 ` [Bug cli/27125] " kelly at 219design dot com 2020-12-29 5:11 ` kelly at 219design dot com 2020-12-29 5:15 ` kelly at 219design dot com 2020-12-29 18:38 ` kelly at 219design dot com 2021-01-05 13:51 ` cbiesinger at google dot com
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=bug-27125-4717-r1Wioyi9qW@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).