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] New: [gdb, aarch64] UNRESOLVED: gdb.python/py-disasm.exp: global_disassembler=ReadMemoryGdbErrorDisassembler: disassemble test
Date: Fri, 21 Oct 2022 10:47:53 +0000 [thread overview]
Message-ID: <bug-29712-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29712
Bug ID: 29712
Summary: [gdb, aarch64] UNRESOLVED: gdb.python/py-disasm.exp:
global_disassembler=ReadMemoryGdbErrorDisassembler:
disassemble test
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On aarch64-linux, I run into:
...
(gdb) PASS: gdb.python/py-disasm.exp:
global_disassembler=ReadMemoryGdbErrorDisassembler: python
add_global_disassembler(ReadMemoryGdbErrorDisassembler)
disassemble test^M
Dump of assembler code for function test:^M
0x00000000004005e4 <+0>: nop^M
terminate called after throwing an instance of 'gdbpy_err_fetch'^M
^M
^M
Fatal signal: Aborted^M
----- Backtrace -----^M
0x55dc4f gdb_internal_backtrace_1^M
/home/tdevries/gdb/src/gdb/bt-utils.c:122^M
0x55dd0f _Z22gdb_internal_backtracev^M
/home/tdevries/gdb/src/gdb/bt-utils.c:168^M
0x739383 handle_fatal_signal^M
/home/tdevries/gdb/src/gdb/event-top.c:964^M
0xffffbe4eb7cb ???^M
0xffffbda48500 ???^M
0xffffbda498a3 ???^M
0xffffbdc74173 ???^M
0xffffbdc71c9b ???^M
0xffffbdc71cff ???^M
0xffffbdc71fe3 ???^M
0x8f1f0f _ZN18gdbpy_disassembler16read_memory_funcEmPhjP16disassemble_info^M
/home/tdevries/gdb/src/gdb/python/py-disasm.c:516^M
0xbd8753 print_insn_aarch64^M
/home/tdevries/gdb/src/opcodes/aarch64-dis.c:3982^M
---------------------^M
A fatal error internal to GDB has been detected, further^M
debugging is not possible. GDB will now terminate.^M
^M
This is a bug, please report it. For instructions, see:^M
<https://www.gnu.org/software/gdb/bugs/>.^M
^M
ERROR: GDB process no longer exists
GDB process exited with wait status 20369 exp48 0 0 CHILDKILLED SIGABRT SIGABRT
UNRESOLVED: gdb.python/py-disasm.exp:
global_disassembler=ReadMemoryGdbErrorDisassembler: disassemble test
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-21 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 10:47 vries at gcc dot gnu.org [this message]
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
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@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).