From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id A21FC3857C70; Tue, 29 Dec 2020 05:11:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A21FC3857C70
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 05:11:25 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: cli
X-Bugzilla-Version: 9.2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kelly at 219design dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-27125-4717-R1vRKb2KRj@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27125-4717@http.sourceware.org/bugzilla/>
References: <bug-27125-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Dec 2020 05:11:25 -0000

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

--- Comment #2 from kelly at 219design dot com ---
prior to commit b0f492b90f3d13da8a, we had:


  if (batch_flag)
    {
      /* We have hit the end of the batch file.  */
      quit_force (NULL, 0);
    }


after that commit, we have (and currently still have):

  if (batch_flag)
    {
      int error_status =3D EXIT_FAILURE;
      int *exit_arg =3D ret =3D=3D 0 ? &error_status : NULL;

      /* We have hit the end of the batch file.  */
      quit_force (exit_arg, 0);
    }

In the absence of "-return-child-result", I wholeheartedly agree with the
outcome of commit b0f492b90f3d13da8a.

When using "-return-child-result", however, it isn't obvious to me whether =
the
new behavior is best.

I would pose the question to users of "-return-child-result":

When "-return-child-result" is active, should that result in executing the =
old
(pre-b0f492b90f3d13da8a) behavior of quit_force? The first variation shown
above?

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