From: Joern Rennecke <joern.rennecke@superh.com>
To: Fernando Nasser <fnasser@redhat.com>,
gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: sh-elf disassembly broken (Was: Re: RFC: Moving disassembler_command to cli land and using newer disassembler code)
Date: Mon, 24 Feb 2003 20:23:00 -0000 [thread overview]
Message-ID: <3E5A7F58.8C87B17D@superh.com> (raw)
In-Reply-To: <3E231F8E.72AA3D4A@superh.com>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
I wrote:
>
> This patch:
>
> 2002-11-07 Fernando Nasser <fnasser@redhat.com>
>
> * printcmd.c (disassemble_command): Remove obsolete function.
> (_initialize_printcmd): Do not create disassemble command here.
> * cli/cli-cmds.c (disassemble_command): New function. Implements
> disassemble command.
> (init_cli_cmds): Create disassemble command here instead.
>
> breaks disassembly for sh-elf (just try to disassemble any
> function in any sh-elf object file).
>
> gdb_disassembly uses TARGET_PRINT_INSN_INFO->mach to initialize
> di.mach, but TARGET_PRINT_INSN_INFO->mach is never initialized.
>
> Before your patch, print_insn had set TARGET_PRINT_INSN_INFO->mach
> to TARGET_ARCHITECTURE->mach, which gets expanded to
> (gdbarch_bfd_arch_info (current_gdbarch))->mach .
And didn't get any reply.
So I had a go at writing a conservative patch, which handles the mach
field likee tui/tuiDisassem.c:tui_disassemble .
Although I have the feeling that TARGET_PRINT_INSN_INFO should be really
a local variable of print_insn, and if any information might be missing
in the gdbarch struct to initialize TARGET_PRINT_INSN_INFO and asm_info
in tui/tuiDisassem.c:tui_disassemble , that should rather be added to
the gdbarch struct.
--
--------------------------
SuperH (UK) Ltd.
2410 Aztec West / Almondsbury / BRISTOL / BS32 4QX
T:+44 1454 465658
[-- Attachment #2: disas-diff --]
[-- Type: text/plain, Size: 992 bytes --]
Mon Feb 24 19:59:50 2003 J"orn Rennecke <joern.rennecke@superh.com>
* disasm.c (gdb_disassembly): If TARGET_ARCHITECTURE is non-zero,
initialize di.mach from there.
Index: disasm.c
===================================================================
RCS file: /cvs/src/src/gdb/disasm.c,v
retrieving revision 1.4
diff -p -r1.4 disasm.c
*** disasm.c 3 Feb 2003 01:18:37 -0000 1.4
--- disasm.c 24 Feb 2003 19:59:47 -0000
*************** gdb_disassembly (struct ui_out *uiout,
*** 338,344 ****
--- 338,350 ----
di_initialized = 1;
}
+ /* ??? TARGET_PRINT_INSN_INFO is undocumented and only initialized inside
+ printcmd.c:print_insn , and some strange hacks that access fields of
+ the variable that underlies the implementation of this macro. */
di.mach = TARGET_PRINT_INSN_INFO->mach;
+ if (TARGET_ARCHITECTURE != NULL)
+ di.mach = TARGET_ARCHITECTURE->mach;
+
if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
di.endian = BFD_ENDIAN_BIG;
else
next parent reply other threads:[~2003-02-24 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E231F8E.72AA3D4A@superh.com>
2003-02-24 20:23 ` Joern Rennecke [this message]
2003-02-24 21:49 ` Elena Zannoni
2003-02-24 22:07 ` Joern Rennecke
2003-02-24 22:11 ` Elena Zannoni
2003-03-07 18:01 ` Joern Rennecke
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=3E5A7F58.8C87B17D@superh.com \
--to=joern.rennecke@superh.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
/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