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 tdep/29432] New: [gdb, tdep/s390x] Self test failed: self-test failed at arm-tdep.c:14482 (selftest arm-record) Date: Sat, 30 Jul 2022 08:08:11 +0000 [thread overview] Message-ID: <bug-29432-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29432 Bug ID: 29432 Summary: [gdb, tdep/s390x] Self test failed: self-test failed at arm-tdep.c:14482 (selftest arm-record) Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- The gdb-fedora-s390x buildbot fails, alternatively with checkout problems and an actual failure. For an example of the latter, see https://builder.sourceware.org/buildbot/#/builders/75/builds/839 : ... Ran 3640 unit tests, 1 failed (gdb) PASS: gdb.gdb/unittest.exp: no executable loaded: maintenance selftest, ran some tests FAIL: gdb.gdb/unittest.exp: no executable loaded: maintenance selftest, failed none ... In more detail: ... Running selftest arm-record. Process record and replay target doesn't support syscall number -2036195 Process record does not support instruction 0x7f70ee1d at address 0x0. Self test failed: self-test failed at ../../binutils-gdb/gdb/arm-tdep.c:14482 ... The failure is in the "ret == 0" selftest: ... static const uint16_t insns[] = { /* 1d ee 70 7f mrc 15, 0, r7, cr13, cr0, {3} */ 0xee1d, 0x7f70, }; enum bfd_endian endian = gdbarch_byte_order_for_code (arm_record.gdbarch); instruction_reader_thumb reader (endian, insns); int ret = decode_insn (reader, &arm_record, THUMB2_RECORD, THUMB2_INSN_SIZE_BYTES); SELF_CHECK (ret == 0); SELF_CHECK (arm_record.mem_rec_count == 0); SELF_CHECK (arm_record.reg_rec_count == 1); SELF_CHECK (arm_record.arm_regs[0] == 7); ... Note that the: ... Process record does not support instruction 0x7f70ee1d at address 0x0. ... message corresponds to the insns array. Hm, process record seems to think that it's one insn, while in fact there are two. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-30 8:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-30 8:08 vries at gcc dot gnu.org [this message] 2022-07-30 8:08 ` [Bug tdep/29432] " vries at gcc dot gnu.org 2022-07-30 9:26 ` vries at gcc dot gnu.org 2022-07-30 11:29 ` [Bug tdep/29432] [gdb, tdep/s390x/ppc64] " mark at klomp dot org 2022-08-03 11:56 ` mark at klomp dot org 2022-08-03 11:58 ` luis.machado at arm dot com 2022-08-03 11:58 ` luis.machado at arm dot com 2022-08-08 10:16 ` luis.machado at arm dot com 2022-09-07 17:25 ` vries at gcc dot gnu.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-29432-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).