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 python/29712] [gdb, aarch64] UNRESOLVED: gdb.python/py-disasm.exp: global_disassembler=ReadMemoryGdbErrorDisassembler: disassemble test
Date: Mon, 24 Oct 2022 09:17:33 +0000 [thread overview]
Message-ID: <bug-29712-4717-Pa5D2nAmCv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29712-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29712
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #6)
> (In reply to Andrew Burgess from comment #5)
> > Created attachment 14411 [details]
> > Possible patch for this problem
> >
> > Here's my proposal for fixing this issue. This patch avoids the throw/catch
> > over libopcode. I've tested this on aarch64 and it seems to fix the issue.
> > I'm still running the full testsuite.
>
> Thanks.
>
> I'll submit the patch from comment 1.
https://sourceware.org/pipermail/gdb-patches/2022-October/193067.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-24 9:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 10:47 [Bug python/29712] New: " vries at gcc dot gnu.org
2022-10-21 13:09 ` [Bug python/29712] " vries at gcc dot gnu.org
2022-10-21 13:43 ` vries at gcc dot gnu.org
2022-10-21 14:11 ` vries at gcc dot gnu.org
2022-10-21 14:18 ` vries at gcc dot gnu.org
2022-10-21 20:54 ` aburgess at redhat dot com
2022-10-22 4:31 ` vries at gcc dot gnu.org
2022-10-24 9:17 ` vries at gcc dot gnu.org [this message]
2022-10-24 12:51 ` aburgess at redhat dot com
2022-10-31 18:17 ` brobecker at gnat dot com
2022-11-02 7:12 ` luis.machado at arm dot com
2022-11-28 19:24 ` cvs-commit at gcc dot gnu.org
2022-11-28 19:24 ` cvs-commit at gcc dot gnu.org
2022-12-01 18:10 ` tromey at sourceware dot org
2022-12-02 16:39 ` aburgess at redhat 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-29712-4717-Pa5D2nAmCv@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).