gem5.debug fs.py --kernel=riscv.elf --wait-gdb
On 6/15/23 22:17, wanghw364 via gem5-users wrote:
Hi,
Does gem5 riscv support remote gdb to debug the target riscv elf?
I tried in this way but riscv gdb can't connect gem5 and showed
connection time out and gem5 keep running the elf to the end:
1
Hi,
Does gem5 riscv support remote gdb to debug the target riscv elf?
I tried in this way but riscv gdb can't connect gem5 and showed connection time
out and gem5 keep running the elf to the end:
1. ./build/RISCV/gem5.debug --listener-mode=on --allow-remote-connections
--remote-gdb-port=7000 ./c
I don’t know. fs.py isn’t really regularly tested or maintained. it will be
deprecated come v23.0 of gem5. I wouldn’t recommend using it but you’re free to
give it a try if you wish.
--
Dr. Bobby R. Bruce
Room 3050,
Kemper Hall, UC Davis
Davis,
CA, 95616
web: https://www.bobbybruce.net
> On J
Thank you, I'll try it. Is there also a way to run the PARSEC benchmark
through fs.py if I have a disk image loaded with the benchmark?
On Thu, Jun 15, 2023 at 12:11 PM Bobby Bruce via gem5-users <
gem5-users@gem5.org> wrote:
> In the standard library the X86 Board currently doesn’t support memor
In the standard library the X86 Board currently doesn’t support memory sizes
>3GB. The reason for this is due to restrictions in how we setup the memory
ranges of the system.
If you look at the code here:
https://github.com/gem5/gem5/blob/55cecfc3e8fb2bdddfd96a850b0fdaca9bcdd0b3/src/python/gem
The error has been resolved. Turns out I didn't specify the partition on
the disk image. But I'm still wondering if there's any code for running the
benchmark with a system with >3GB main memory.
On Wed, Jun 14, 2023 at 4:20 PM Vincent Abraham
wrote:
> Also, I'm getting the following error on ru
