public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rohanahmed212212 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31406] New: added custom instructions in riscv-gnu-toolchain is not showing in layout asm
Date: Fri, 23 Feb 2024 17:44:18 +0000	[thread overview]
Message-ID: <bug-31406-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31406
           Summary: added custom instructions in riscv-gnu-toolchain is
                    not showing in layout asm
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: rohanahmed212212 at gmail dot com
  Target Milestone: ---

Hey, I am having an issue related to the layout asm

I added my custom instructions in the riscv-gnu-toolchain. The toolchain works
perfectly and my newly added instruction is also recognized by toolchain,
verified by,creating a dump file(Disassembly) having my instruction name rather
than their machine code. 

But, while debuggung with gdb, the machine code(.byte 0xfabad..) is showing in
layout asm instead of my instruction name.

How will I cater this problem?

I already filed an issue in riscv-gnu-toolchain but they said this is not a
RISCV-V specific issue. You can find our discussions in this thread 

https://github.com/riscv-collab/riscv-gnu-toolchain/issues/1412#issuecomment-1948378124

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

             reply	other threads:[~2024-02-23 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 17:44 rohanahmed212212 at gmail dot com [this message]
2024-04-15 12:14 ` [Bug gdb/31406] " rohanahmed212212 at gmail dot com
2024-04-15 12:15 ` rohanahmed212212 at gmail dot com
2024-04-15 12:16 ` rohanahmed212212 at gmail dot com

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-31406-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).