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: Sat, 19 Nov 2022 07:11:37 +0000	[thread overview]
Message-ID: <bug-29793-4717-TqsYqW6Lr0@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 #16 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Carl E Love from comment #15)
> I tried to apply the patch to the very latest GDB tree.  It doesn't apply. 
> Just wanted to see if I could help test the proposed patch.

Hi Carl, that would be great.

I've clicked on the link, then on "Raw Unified" which got me here (
https://sourceware.org/bugzilla/attachment.cgi?id=14461&action=diff&collapsed=&headers=1&format=raw
).

Then I saved as text file, which got me attachment.txt.

Then I applied onto recent commit 5e219e0f460 ("gdbserver/linux-x86: move lwp
declaration out of __x86_64__ region"):
...
$ patch -p1 < attachment.txt 
patching file gdb/breakpoint.c
$ 
...

So, that works for me.

Then I tried "View", which got me here (
https://sourceware.org/bugzilla/attachment.cgi?id=14461 ).

I saved as text file to
0001-gdb-tdep-Fix-gdb.cp-gdb2495.exp-on-powerpc64le.txt.

Then I applied onto the same commit:
...
$ git am 0001-gdb-tdep-Fix-gdb.cp-gdb2495.exp-on-powerpc64le.txt
Applying: Fix gdb.cp/gdb2495.exp on powerpc64le
$ 
...

So, unfortunately I'm not able to reproduce your problem in applying.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-11-19  7:11 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
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 [this message]
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-TqsYqW6Lr0@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).