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 979543857C7C; Mon, 13 Dec 2021 10:35:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 979543857C7C
From: "luis.machado at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28549] ARM/Cortex-M: improper stack unwinding when the
 target is in lockup state
Date: Mon, 13 Dec 2021 10:35:55 +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: 9.2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luis.machado at linaro dot org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: luis.machado at linaro dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-28549-4717-Gf0u27ZCWK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28549-4717@http.sourceware.org/bugzilla/>
References: <bug-28549-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, 13 Dec 2021 10:35:55 -0000

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

--- Comment #18 from Luis Machado <luis.machado at linaro dot org> ---
What I meant by elegance is making GDB stop when it should and display the
right information (that we're locked up, instead of appearing like we stopp=
ed
in the middle of a signal handler).

If GDB attempts to backtrace further (as you showed in your example), that
sounds like a problem with the patch. It should've acted like the following=
...

--

(gdb) c
Continuing.
stm32h7x.cpu0 -- clearing lockup after double fault

Program received signal SIGINT, Interrupt.
<signal handler called>
(gdb)

--

... which, in my opinion, is not as informative as displaying a custom mess=
age
saying we're locked up.

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