I switch between waiting and non-waiting scenario many times per day.
The BaseCPU.wait_for_remote_gdb attribute, introduced in
c2baaab0ed,
makes it much less painful by saving many recompiles.
The present commit tries to go a bit further: the se.py script is
under version control, and changing it interferes with smooth git
workflow.
Change-Id: Ie65ffc44b11d78d5e7878f81f2fcdafa143c20a8
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/27287
Tested-by: Gem5 Cloud Project GCB service account <345032938727@cloudbuild.gserviceaccount.com>
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Maintainer: Jason Lowe-Power <power.jg@gmail.com>
"to be used in syscall emulation."
"Usage: gem5.opt [...] --redirects /dir1=/path/"
"to/host/dir1 --redirects /dir2=/path/to/host/dir2")
+ parser.add_option("--wait-gdb", default=False,
+ help="Wait for remote GDB to connect.")
MemConfig.config_mem(options, system)
config_filesystem(system, options)
+if options.wait_gdb:
+ for cpu in system.cpu:
+ cpu.wait_for_remote_gdb = True
+
root = Root(full_system = False, system = system)
Simulation.run(options, root, system, FutureClass)