You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2020. It is now read-only.
Hi Ameya,
I apologize for not documenting how to use the --gdb option. I will do so
later today. Meanwhile, here's a quick howto:
1. You need to use gdb from the riscv toolchain.
2. If your target riscv program is xyz, then you would issue the command:
gdb xyz
3. Then you would issue the gdb command: target remote | whisper --gdb xyz
Joe
On Thu, Jan 3, 2019 at 5:00 AM Ameya Vikram Singh ***@***.***> wrote:
Hello,
I have a query regarding the command line option: --gdb.
How do I use the option to enable remote GDB session?
Currently I have observed the GDB output on stdout.
I have written a script which redirect the whisper simulator stdout and
stdin through netcat.
But it is an inelegant solution since, I lose any stdout prints from
riscv binaries linked with newlib.
Thank you for the assistance.
-Ameya Vikram Singh
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACR4X397S6zlllBXcmGl8mo_h979AC-oks5u_eLNgaJpZM4Zn5ir>
.
Hello,
I have a query regarding the command line option:
--gdb
.How do I use the option to enable remote GDB session?
Currently I have observed the GDB output on stdout.
I have written a script which redirect the
whisper
simulatorstdout
andstdin
throughnetcat
.But it is an inelegant solution since, I lose any
stdout
prints from riscv binaries linked with newlib.Thank you for the assistance.
-Ameya Vikram Singh
The text was updated successfully, but these errors were encountered: