public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13000] Return value with -batch is always 0
Date: Sun, 31 Dec 2023 12:23:59 +0000	[thread overview]
Message-ID: <bug-13000-4717-Endh5Vf9cv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13000-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=13000

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
   Target Milestone|---                         |8.3
                 CC|                            |ssbssa at sourceware dot org

--- Comment #7 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Sourceware Commits from comment #6)
> The master branch has been updated by Gary Benson <gary@sourceware.org>:
> 
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=b0f492b90f3d13da8ac80437e6ecb9a87db4a75b
> 
> commit b0f492b90f3d13da8ac80437e6ecb9a87db4a75b
> 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.

Was fixed with this commit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-12-31 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 20:44 [Bug gdb/13000] New: " michel.metzger at st dot com
2014-06-25 12:23 ` [Bug gdb/13000] " tuben at lysator dot liu.se
2015-06-04 13:35 ` arma2ff0 at gmail dot com
2015-06-04 13:51 ` arma2ff0 at gmail dot com
2015-06-04 18:12 ` dje at google dot com
2015-06-05 11:50 ` arma2ff0 at gmail dot com
2023-12-31 12:23 ` ssbssa at sourceware dot org [this message]

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-13000-4717-Endh5Vf9cv@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: link
Be 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).