public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.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 [thread overview]
Message-ID: <bug-27330-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27330
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 = obj->separate_debug_objfile;
> + sepdebug != nullptr; sepdebug = 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.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-02-03 8:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 8:53 vries at gcc dot gnu.org [this message]
2021-02-03 8:55 ` [Bug breakpoints/27330] " vries at gcc dot gnu.org
2021-02-03 9:57 ` vries at gcc dot gnu.org
2021-02-05 12:30 ` vries at gcc dot gnu.org
2021-02-05 16:47 ` cvs-commit at gcc dot gnu.org
2021-02-05 19:54 ` cvs-commit at gcc dot gnu.org
2021-02-05 19:55 ` vries at gcc dot gnu.org
2021-06-27 17:44 ` ahmedsayeed1982 at yahoo dot com
2021-09-02 11:06 ` donipah907 at mtlcz dot com
2021-09-02 11:15 ` mark at klomp dot org
2021-09-05 7:34 ` kimolsun2020 at yahoo dot com
2021-09-05 7:41 ` vries at gcc dot gnu.org
2021-09-06 9:08 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:38 ` mehmetgelisin at aol dot com
2021-09-20 12:03 ` lisawelch939 at gmail dot com
2021-09-22 10:19 ` diheto5497 at secbuf dot com
2021-09-26 13:31 ` tes.vik1986 at gmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-09 17:03 ` studiaviktor at gmail dot com
2021-10-18 19:58 ` ahmedsayeed1982 at hotmail dot com
2021-10-19 7:14 ` progonsaytu at gmail dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-11-24 13:43 ` allen at rockvalleymarketing dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27330-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).