public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27736] New: Gdb really needs an enhanced assembly stepping mode
Date: Thu, 15 Apr 2021 18:19:59 +0000	[thread overview]
Message-ID: <bug-27736-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27736
           Summary: Gdb really needs an enhanced assembly stepping mode
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: keiths at redhat dot com
  Target Milestone: ---

>From https://bugzilla.redhat.com/show_bug.cgi?id=1859714 :

Gdb really needs an enhanced assembly stepping mode that will print,
not just the instructions themselves, but also the inputs and outputs.

For example, on POWER, if the current instruction is add r9, r1, r2:

(gdb) stepi
    # would print
<address expression>:     <previous instruction>
    r1 = 15 (0x0F)  r2 = 14 (0x0E)
<current address>:        add  r9, r1, r2
    r9 = 29 (0x1D)
<address expression>:     <next instruction>

(gdb)

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

             reply	other threads:[~2021-04-15 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 18:19 keiths at redhat dot com [this message]
2021-04-15 19:02 ` [Bug gdb/27736] " keiths at redhat dot com
2021-04-15 20:13 ` tromey at sourceware dot org
2021-04-16 15:14 ` ssbssa at sourceware 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-27736-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).