From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 89CCD381DCCC; Wed, 3 Feb 2021 08:53:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89CCD381DCCC From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/27330] New: nextoverthrow.exp FAILs on arm-none-eabi Date: Wed, 03 Feb 2021 08:53:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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 List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2021 08:53:48 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27330 Bug ID: 27330 Summary: nextoverthrow.exp FAILs on arm-none-eabi Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Reported by Abid here ( https://sourceware.org/pipermail/gdb-patches/2021-February/175699.html ): ... I observed that nextoverthrow.exp is now failing for many targets including arm-none-eabi after this change. > + /* Iterate over separate debug objects and try an _Unwind_DebugHook > + kind breakpoint. */ > + for (objfile *sepdebug =3D obj->separate_debug_objfile; > + sepdebug !=3D nullptr; sepdebug =3D sepdebug->separate_debug_objfile) > + if (create_exception_master_breakpoint_hook (sepdebug)) > + break; This bit seems to be problematic as it is stopping exception breakpoint to be installed when separate_debug_objfile is null. ... --=20 You are receiving this mail because: You are on the CC list for the bug.=