From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E027B385842E; Wed, 14 Sep 2022 12:10:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E027B385842E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1663157446; bh=dQnJMNjGy2zY2vT1TMhyjt4FTShIa16jcNEq/zRw/hI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=r4Hbmm0Wxrqc19ugLqrcu9nr7XEvo9lyj02EkAknp07ZAEZ/vrwCZuAhOzTre0EE4 j/RvL3AmcJKD3tVXmeE9Ru2/yXlviwQR/JjKBl+oegbdhR48g2oXFsTbzmU1QWpVq1 M+5aQajeVP5RT0gGuppjzhQ9RHPe0rgJB9aSnTOI= From: "luis.machado at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/28549] ARM/Cortex-M: improper stack unwinding when the target is in lockup state Date: Wed, 14 Sep 2022 12:10:46 +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 arm dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: luis.machado at arm dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D28549 --- Comment #43 from Luis Machado --- (In reply to tomas.vanek from comment #42) > (In reply to Luis Machado from comment #41) >=20 > > You'll need a FSF copyright > > assignment in place to be able to contribute non-trivial changes. Do you > > have one? >=20 > No, I do not. >=20 You will need to get one (or be covered by one by your employer, if there is one). More information here: https://sourceware.org/gdb/wiki/ContributionChecklis= t, item 6. If you don't want to do it, someone else with copyright assignment in place will need to write their own code to implement this change. > > As for the change, here's what git shows for that commit: >=20 > Thanks, I've already seen the code in the current git master. > I asked to find if there is some new pending work not yet merged to master > branch. Ah, sorry. I misunderstood. No, I don't think there are further changes pla= nned for this particular piece of code. --=20 You are receiving this mail because: You are on the CC list for the bug.=