-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automate passing set arch riscv:rv32
to gdb?
#101
Comments
This is the same issue as riscvarchive/riscv-binutils-gdb#54 (which is not being worked on :-( ). |
ok, at least we know the cause. |
riscvarchive/riscv-binutils-gdb#54 was fixed. |
Thank you, Tim. When do you think you'll have a new official release of GDB and OpenOCD, with all these goodies? |
This change is in riscv-tools now.
…On Wed, Dec 27, 2017 at 2:35 PM, Liviu Ionescu ***@***.***> wrote:
Thank you, Tim.
When do you think you'll have a new official release of GDB and OpenOCD,
with all these goodies?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#101 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APYH7VqQ6wzMaPrgR8JBOcrPJYwRI8X9ks5tEsYWgaJpZM4O4hX2>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that when starting GDB for a RISC-V debug session I have to pass a command like:
similarly, when starting debug sessions with ARM devices, setting the architecture is not necessary.
it looks like OpenOCD is able to automatically inform GDB what the architecture is, but this feature is not used for RISC-V devices.
is there anything to do to automate passing the architecture for RISC-V devices too?
The text was updated successfully, but these errors were encountered: