public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "kip at thevertigo dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28486] [riscv64] GDB doesn't allow stepping over cbreak trap instruction
Date: Fri, 22 Oct 2021 05:43:17 +0000	[thread overview]
Message-ID: <bug-28486-4717-v3t6AhiNSD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28486-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Kip Warner <kip at thevertigo dot com> ---
Hey Jim,

Sorry, there was a typo in my original post. I meant ebreak, not cbreak.

I tried the semihosting trap instruction sequence and I still had the same
result on the ebreak instruction:

    asm volatile("slli x0, x0, 0x1f; ebreak; srai x0, x0, 7");

While folks figure out whether this is a bug in GDB or intentional, do you have
a suggested workaround for what I'm trying to achieve? I'm aware of the kill()
and raise() functions, but they require an #include, whereas inline asm rolled
into a #define macro does not.

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

  parent reply	other threads:[~2021-10-22  5:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 20:25 [Bug gdb/28486] New: " kip at thevertigo dot com
2021-10-21 22:38 ` [Bug gdb/28486] " wilson at gcc dot gnu.org
2021-10-22  5:43 ` kip at thevertigo dot com [this message]
2021-10-25 20:53 ` wilson at gcc dot gnu.org
2021-10-25 21:14 ` kip at thevertigo dot com
2022-04-09 15:03 ` [Bug tdep/28486] " tromey 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-28486-4717-v3t6AhiNSD@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).