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 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 18:53:06 +0000 [thread overview] Message-ID: <bug-29793-4717-OXUqYPH9d9@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 #4 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Carl E Love from comment #2) > I have been trying to work my way thru the list of GDB failures on > PowerPC for the last year+. Yes, I noticed, much appreciated :) > We have made good progress reducing the > number of failures on PowerPC. Agreed. If I run the testsuite and grep -v the gdb.reverse fails, there are not a lot of fails left. > I am trying to finish up a patch for > gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp then OK, good to know. > I hope to get back to this bug and the issue with gdb.base/store.exp. Ack. I don't see the gdb.base/store.exp one though, could you file a PR for that? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-16 18:53 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 2022-11-16 18:35 ` vries at gcc dot gnu.org 2022-11-16 18:53 ` vries at gcc dot gnu.org [this message] 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-OXUqYPH9d9@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: linkBe 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).