public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb] Fix warning in print_one_insn::ez80-adl Date: Sat, 4 Jun 2022 09:11:41 +0000 (GMT) [thread overview] Message-ID: <20220604091141.C849A3856081@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=98c17098021554b3394ba052e94d9f1243ae37c2 commit 98c17098021554b3394ba052e94d9f1243ae37c2 Author: Tom de Vries <tdevries@suse.de> Date: Sat Jun 4 11:11:37 2022 +0200 [gdb] Fix warning in print_one_insn::ez80-adl When running selftest print_one_insn::ez80-adl we run into this warning: ... Running selftest print_one_insn::ez80-adl. warning: Unable to determine inferior's software breakpoint type: couldn't find `_break_handler' function in inferior. Will be used default software \ breakpoint instruction RST 0x08. ... Fix this by explicitly handling bfd_arch_z80 in print_one_insn_test. Tested on x86_64-linux. Diff: --- gdb/disasm-selftests.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/gdb/disasm-selftests.c b/gdb/disasm-selftests.c index 7daa0138f6f..b3c5d997720 100644 --- a/gdb/disasm-selftests.c +++ b/gdb/disasm-selftests.c @@ -86,6 +86,13 @@ print_one_insn_test (struct gdbarch *gdbarch) if (gdbarch_bfd_arch_info (gdbarch)->mach == bfd_mach_arc_arc601) return; goto generic_case; + case bfd_arch_z80: + { + int bplen; + insn = gdbarch_sw_breakpoint_from_kind (gdbarch, 0x0008, &bplen); + len = bplen; + } + break; case bfd_arch_i386: { const struct bfd_arch_info *info = gdbarch_bfd_arch_info (gdbarch);
reply other threads:[~2022-06-04 9:11 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220604091141.C849A3856081@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@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).