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 B49283840038; Mon, 26 Jul 2021 06:49:20 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B49283840038
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/28076] [regression] Cannot remove condition from breakpoint
 from MI
Date: Mon, 26 Jul 2021 06:49:20 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: mi
X-Bugzilla-Version: 11.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tankut.baris.aktemur at intel dot com
X-Bugzilla-Target-Milestone: 11.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-28076-4717-xL5jD2hVhC@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28076-4717@http.sourceware.org/bugzilla/>
References: <bug-28076-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: Mon, 26 Jul 2021 06:49:20 -0000

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

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gn=
u.org> ---
The master branch has been updated by Tankut Baris Aktemur
<aktemur@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Db6c420514982=
4bfc3e5ab9e12819dcc0fc2af29d

commit b6c4205149824bfc3e5ab9e12819dcc0fc2af29d
Author: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
Date:   Mon Jul 26 08:25:03 2021 +0200

    gdb/mi: handle no condition argument case for -break-condition

    As reported in PR gdb/28076 [1], passing no condition argument to the
    -break-condition command (e.g.: "-break-condition 2") should clear the
    condition for breakpoint 2, just like CLI's "condition 2", but instead
    an error message is returned:

      ^error,msg=3D"-break-condition: Missing the <number> and/or <expr>
argument"

    The current implementation of the -break-condition command's argument
    handling (79aabb7308c "gdb/mi: add a '--force' flag to the
    '-break-condition' command") was done according to the documentation,
    where the condition argument seemed mandatory.  However, the
    -break-condition command originally (i.e. before the 79aabb7308c
    patch) used the CLI's "cond" command, and back then not passing a
    condition argument was clearing out the condition.  So, this is a
    regression in terms of the behavior.

    Fix the argument handling of the -break-condition command to allow not
    having a condition argument, and also update the document to make the
    behavior clear.  Also add test cases to test the scenarios which were
    previously not covered.

    [1] https://sourceware.org/bugzilla/show_bug.cgi?id=3D28076

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