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 gdb/30518] New: [gdb, i586] FAIL: gdb.python/py-disasm.exp: memory source api: second disassembler pass
Date: Tue, 06 Jun 2023 09:26:12 +0000	[thread overview]
Message-ID: <bug-30518-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30518

            Bug ID: 30518
           Summary: [gdb, i586] FAIL: gdb.python/py-disasm.exp: memory
                    source api: second disassembler pass
           Product: gdb
           Version: 13.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With a gdb 13.1 based package, on i586 native I run into:
...
(gdb) PASS: gdb.python/py-disasm.exp: memory source api: python
analyzing_disassembler = add_global_disassembler(AnalyzingDisassembler)
disassemble test^M
Dump of assembler code for function test:^M
   0x080483f6 <+0>:     push   %ebp^M
   0x080483f7 <+1>:     mov    %ecx,-0x6f6f1a77(%ecx)^M
   0x080483fd <+7>:     add    %al,(%eax)^M
   0x080483ff <+9>:     add    %al,(%eax)^M
   0x08048401 <+11>:    pop    %ebp^M
   0x08048402 <+12>:    ret^M
End of assembler dump.^M
(gdb) FAIL: gdb.python/py-disasm.exp: memory source api: disassemble test
...

Note that something like this, executed earlier works fine:
...
(gdb) PASS: gdb.python/py-disasm.exp: global_disassembler=: python
remove_all_python_disassemblers()
disassemble test^M
Dump of assembler code for function test:^M
   0x080483f6 <+0>:     push   %ebp^M
   0x080483f7 <+1>:     mov    %esp,%ebp^M
   0x080483f9 <+3>:     nop^M
=> 0x080483fa <+4>:     nop^M
   0x080483fb <+5>:     nop^M
   0x080483fc <+6>:     mov    $0x0,%eax^M
   0x08048401 <+11>:    pop    %ebp^M
   0x08048402 <+12>:    ret^M
End of assembler dump.^M
(gdb) PASS: gdb.python/py-disasm.exp: global_disassembler=: disassemble test
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-06-06  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  9:26 vries at gcc dot gnu.org [this message]
2023-08-29 11:11 ` [Bug gdb/30518] " 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-30518-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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).