public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27891] New: maintenance selftest fail when an executable is loaded Date: Thu, 20 May 2021 13:21:05 +0000 [thread overview] Message-ID: <bug-27891-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27891 Bug ID: 27891 Summary: maintenance selftest fail when an executable is loaded Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: andrew.burgess at embecosm dot com Target Milestone: --- I built GDB with --enable-targets=all, and am running on an x86-64 GNU/Linux host. If I start GDB and load an executable (for example GDB itself), and then run 'maint selftest', I see 1 failure. In contrast, if I start GDB and don't load an executable, I see 0 failures. Here's the error(s) that I see: Running selftest print_one_insn. Self test failed: arch arm: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv2: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv2a: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv3: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv3m: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv4: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv4t: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv5: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv5t: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv5te: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch xscale: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch ep9312: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch iwmmxt: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch iwmmxt2: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv5tej: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv6: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv6kz: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv6t2: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv6k: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv7: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv6-m: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv6s-m: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv7e-m: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv8-a: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv8-r: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv8-m.base: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv8-m.main: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch armv8.1-m.main: self-test failed at ../../src/gdb/disasm-selftests.c:165 Self test failed: arch arm_any: self-test failed at ../../src/gdb/disasm-selftests.c:165 warning: A handler for the OS ABI "GNU/Linux" is not built into this configuration of GDB. Attempting to continue with the default cris:common_v10_v32 settings. Self test failed: self-test failed at ../../src/gdb/selftest-arch.c:85 I had a quick look and it appears that the ARM disassembler gets into a state where it thinks it is disassembling in thumb mode. When there is no executable loaded this is not the case. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-05-20 13:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-20 13:21 andrew.burgess at embecosm dot com [this message] 2021-09-13 10:32 ` [Bug gdb/27891] " vries at gcc dot gnu.org 2021-09-13 11:23 ` vries at gcc dot gnu.org 2021-09-13 12:14 ` luis.machado at linaro dot org 2021-09-13 19:43 ` vries at gcc dot gnu.org 2021-09-13 19:45 ` luis.machado at linaro dot 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-27891-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: 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).