aboutsummaryrefslogtreecommitdiff
path: root/debug/gdbserver.py
diff options
context:
space:
mode:
authorTim Newsome <tim@sifive.com>2018-04-09 13:09:55 -0700
committerTim Newsome <tim@sifive.com>2018-04-09 13:11:36 -0700
commitdf93b0dc9a6580b4f74a10c50190e008d57f41f4 (patch)
tree944f34d9bb4f98fc804444003a6681547bc5c376 /debug/gdbserver.py
parentd63a6a4ad0057614d1c838c1b506b6fa0032de01 (diff)
downloadriscv-tests-df93b0dc9a6580b4f74a10c50190e008d57f41f4.zip
riscv-tests-df93b0dc9a6580b4f74a10c50190e008d57f41f4.tar.gz
riscv-tests-df93b0dc9a6580b4f74a10c50190e008d57f41f4.tar.bz2
Compute gdb command timeout based on ops estimate
The caller of gdb.command() should estimate how much work gdb needs to do, and testlib then scales this up proportional to the general gdb timeout we configured. This hopefully allows us to configure a tighter timeout, so we don't have to have a multi-hour timeout just for something that takes long like `load` on a really slow simulator. Hopefully this addresses #122.
Diffstat (limited to 'debug/gdbserver.py')
-rwxr-xr-xdebug/gdbserver.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/debug/gdbserver.py b/debug/gdbserver.py
index c7bfbf0..d085e2e 100755
--- a/debug/gdbserver.py
+++ b/debug/gdbserver.py
@@ -835,7 +835,7 @@ class DownloadTest(GdbTest):
def test(self):
self.gdb.load()
self.gdb.command("b _exit")
- self.gdb.c(timeout=60)
+ self.gdb.c()
assertEqual(self.gdb.p("status"), self.crc)
os.unlink(self.download_c.name)