aboutsummaryrefslogtreecommitdiff
path: root/spike_main
diff options
context:
space:
mode:
authorTim Newsome <tim@sifive.com>2016-03-07 15:44:20 -0800
committerTim Newsome <tim@sifive.com>2016-05-23 12:12:09 -0700
commitd1ba8b559309c6e3dd47c18674b199bd3cf6e8d9 (patch)
tree8b314495f8c6c25cba373596c60f2b9ee0bb554c /spike_main
parent206b89737c562a6882a729ae88cfe0ac75862c3c (diff)
downloadspike-d1ba8b559309c6e3dd47c18674b199bd3cf6e8d9.zip
spike-d1ba8b559309c6e3dd47c18674b199bd3cf6e8d9.tar.gz
spike-d1ba8b559309c6e3dd47c18674b199bd3cf6e8d9.tar.bz2
gdb can now read spike memory.
The endianness is wrong, but I think it might be that gdb doesn't have it right. Need to investigate what architecture gdb thinks it's debugging.
Diffstat (limited to 'spike_main')
-rw-r--r--spike_main/spike.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/spike_main/spike.cc b/spike_main/spike.cc
index b7748d6..b0a9a3e 100644
--- a/spike_main/spike.cc
+++ b/spike_main/spike.cc
@@ -74,7 +74,7 @@ int main(int argc, char** argv)
auto argv1 = parser.parse(argv);
std::vector<std::string> htif_args(argv1, (const char*const*)argv + argc);
sim_t s(isa, nprocs, mem_mb, htif_args);
- gdbserver_t gdbserver(9824);
+ gdbserver_t gdbserver(9824, &s);
s.set_gdbserver(&gdbserver);
if (dump_config_string) {