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 guile/30514] New: [gdb/guile] FAIL: gdb.guile/scm-disasm.exp: disassemble via memory port Date: Mon, 05 Jun 2023 13:51:34 +0000 [thread overview] Message-ID: <bug-30514-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30514 Bug ID: 30514 Summary: [gdb/guile] FAIL: gdb.guile/scm-disasm.exp: disassemble via memory port Product: gdb Version: 12.1 Status: NEW Severity: normal Priority: P2 Component: guile Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With a gdb 12.1 based packaged, on i586 and s390x-m31 I run into: ... FAIL: gdb.guile/scm-disasm.exp: memory-port: disassemble FAIL: gdb.guile/scm-disasm.exp: disassemble via memory port ... In more detail: ... (gdb) PASS: gdb.guile/scm-disasm.exp: open memory port guile (define insn-list (arch-disassemble arch pc #:port mem #:size 1 #:count 1))^M ERROR: Cannot access memory at address 0x5655557e^M Error while executing Scheme code.^M (gdb) FAIL: gdb.guile/scm-disasm.exp: memory-port: disassemble ... and: ... (gdb) PASS: gdb.guile/scm-disasm.exp: memory-port: verify correct address guile (define insn-list-mem (arch-disassemble arch pc #:port mem #:size 1 #:count 1))^M ERROR: Cannot access memory at address 0x5655557e^M Error while executing Scheme code.^M (gdb) FAIL: gdb.guile/scm-disasm.exp: disassemble via memory port ... Note that this is the same configuration for which I see PR29241. I haven't been able to reproduce this outside of OBS (Open Build Service). -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2023-06-05 13:51 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=bug-30514-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).