public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29793] [gdb/tdep, powerpc] FAIL: gdb.cp/gdb2495.exp: call a function that raises an exception without a handler.
Date: Wed, 16 Nov 2022 17:39:04 +0000 [thread overview]
Message-ID: <bug-29793-4717-xODWG6WAp3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29793-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29793
--- Comment #2 from Carl E Love <cel at us dot ibm.com> ---
Tom:
On Wed, 2022-11-16 at 17:22 +0000, vries at gcc dot gnu.org wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=29793
>
> --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
> That behaviour is due to create_std_terminate_master_breakpoint:
> ...
> addr = bp_objfile_data->terminate_msym.value_address ();
> b = create_internal_breakpoint (objfile->arch (), addr,
> bp_std_terminate_master);
> ...
> which gets the minimal symbol for std::terminate, and then set a
> breakpoint
> on its address, in other words, it does break *std::terminate.
>
Yes, this is on my list of gdb failures that I am looking at. I have
only been able to spend a little time looking at it before getting
distracted. It looks like you have identified the issue a bit more
than I have so far.
I have been trying to work my way thru the list of GDB failures on
PowerPC for the last year+. We have made good progress reducing the
number of failures on PowerPC. I am trying to finish up a patch for
gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp then
I hope to get back to this bug and the issue with gdb.base/store.exp.
Thanks for the bugzilla.
Carl
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-16 17:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 17:18 [Bug tdep/29793] New: " vries at gcc dot gnu.org
2022-11-16 17:19 ` [Bug tdep/29793] " vries at gcc dot gnu.org
2022-11-16 17:22 ` vries at gcc dot gnu.org
2022-11-16 17:39 ` cel at us dot ibm.com [this message]
2022-11-16 18:35 ` vries at gcc dot gnu.org
2022-11-16 18:53 ` vries at gcc dot gnu.org
2022-11-16 23:01 ` cel at us dot ibm.com
2022-11-17 9:24 ` vries at gcc dot gnu.org
2022-11-17 9:42 ` vries at gcc dot gnu.org
2022-11-17 13:11 ` uweigand at gcc dot gnu.org
2022-11-17 18:03 ` cel at us dot ibm.com
2022-11-18 9:57 ` vries at gcc dot gnu.org
2022-11-18 11:18 ` vries at gcc dot gnu.org
2022-11-18 13:20 ` vries at gcc dot gnu.org
2022-11-18 14:17 ` vries at gcc dot gnu.org
2022-11-18 16:44 ` vries at gcc dot gnu.org
2022-11-18 19:25 ` cel at us dot ibm.com
2022-11-19 7:11 ` vries at gcc dot gnu.org
2022-11-19 11:18 ` vries at gcc dot gnu.org
2022-11-21 16:34 ` cel at us dot ibm.com
2022-11-23 5:52 ` cvs-commit at gcc dot gnu.org
2022-11-23 5:54 ` vries at gcc dot gnu.org
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-29793-4717-xODWG6WAp3@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).