Hi folks, particularly Bobby. I have some changes in review which enable
using gem5's remote GDB support with the fast model CPUs. When I initially
started working on that remote GDB support for ARM was broken, and it would
be nice to avoid the new support for fast models or the existing support
for native gem5 CPUs from breaking in the future.

What would be a good testing strategy for this? It would be nice to avoid
having to have GDB installed on the host machine, and it would need to
support whatever ISA it was being tested with. I see that QEMU uses this
approach though. It uses the python module gdb can be (but is not always)
installed with to automate running commands that attach to and control the
target stub.

Gabe
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to