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 35C653846405; Wed, 27 Jan 2021 16:00:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 35C653846405
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26819] RISC-V: internal-error: int
 finish_step_over(execution_control_state*): Assertion
Date: Wed, 27 Jan 2021 16:00:23 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: andrew.burgess at embecosm dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-26819-4717-TjemVdahR9@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26819-4717@http.sourceware.org/bugzilla/>
References: <bug-26819-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: Wed, 27 Jan 2021 16:00:23 -0000

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

--- Comment #24 from Simon Marchi <simark at simark dot ca> ---
(In reply to Jan Matyas from comment #23)
> Hello,
>=20
> I would like to ask about the status of the latest patch for this issue. =
As
> a newcomer, I am not certain what process is followed to have the patch
> merged. Is there any way I can help the process?
>=20
> Thank you, regards
> Jan

You can if you'd like.  The steps missing are:

- Write a good commit message that explains why things fail currently and w=
hy
the patch fixes them (including a ChangeLog entry)
- Enhance the test (gdb.server/stop-reply-no-thread.exp I think) so it cove=
rs
the two scenarios I mentioned ("--disable-packet=3DT
--disable-packet=3DqfThreadInfo" and "--disable-packet=3Dthreads")
- Send the patch to the mailing list for review.

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