aboutsummaryrefslogtreecommitdiff
path: root/debug/README.md
diff options
context:
space:
mode:
authorTim Newsome <tim@sifive.com>2016-07-28 10:26:47 -0700
committerTim Newsome <tim@sifive.com>2016-07-28 10:34:02 -0700
commit553f2a265fe62b514cb97fdbd80ea1743de6e3cf (patch)
treef165a3ec6b48c587c737b5a8ff25b2ad950b0daf /debug/README.md
parent402d4538783ee7a048809dfa0ce923eca9d3f868 (diff)
downloadriscv-tests-553f2a265fe62b514cb97fdbd80ea1743de6e3cf.zip
riscv-tests-553f2a265fe62b514cb97fdbd80ea1743de6e3cf.tar.gz
riscv-tests-553f2a265fe62b514cb97fdbd80ea1743de6e3cf.tar.bz2
Add --gdb argument so I can run valgrind on gdb.
Diffstat (limited to 'debug/README.md')
-rw-r--r--debug/README.md9
1 files changed, 6 insertions, 3 deletions
diff --git a/debug/README.md b/debug/README.md
index 09662ba..4a90c0c 100644
--- a/debug/README.md
+++ b/debug/README.md
@@ -19,10 +19,10 @@ Targets
`./gdbserver.py --spike32 --cmd $RISCV/bin/spike`
-32-bit SiFive Core on Microsemi FPGA board
-------------------------------------------
+32-bit SiFive Core on Arty FPGA board
+-------------------------------------
-`./gdbserver.py --m2gl_m2s`
+`./gdbserver.py --freedom-e300`
Debug Tips
==========
@@ -36,3 +36,6 @@ to get an idea of what might have gone wrong.
You can see what spike is doing by add `-l` to the spike command, eg.:
`./gdbserver.py --spike32 --cmd "$RISCV/bin/spike -l"
DebugTest.test_breakpoint`. (Then look at spike.log.)
+
+You can run gdb under valgrind by passing --gdb, eg.: `./gdbserver.py --spike64
+--gdb "valgrind riscv64-unknown-elf-gdb" -- -v DownloadTest`.