Thank you Boris, I have used the following GDB flags (as you suggested) to figure out and inspect the data being transmitted to the (host gdb) from Gem5 and vice versa.
--debug-flag=GDBSend,GDBRecv,GDBMisc When I set a breakpoint at a specific location in the code (say function call) that is located at address offset (e.g., 1031e) and hit enter, a bunch of information is send to Gem5 as following: 0: system.remote_gdb: recv: m1031e,2 // receive 0: system.remote_gdb: send: fff7 // send what ??? 0: system.remote_gdb: recv: Z0,1031e,3 // receive I know that the gem5 has received data from (host gdb) which tell it to set a breakpoint at instruction located at offset 1031e. BUT WHAT does the number three mean here? Because I think it is the main cause of the problem; when I hit cont at (host gdb) the program at gem5 side never stops and finishes its work with the mentioned warn message: warn: Invalid breakpoint length WHAT is the valid length? and how to adjust it? if I set a bp at another location (say at a place of printf instruction), also I got an error. 0: system.remote_gdb: set software breakpoint, addr=0x1030a, len=2 warn: Invalid breakpoint length Additional info available are available here: https://stackoverflow.com/questions/65943323/remote-gdb-with-gem5 _______________________________________________ gem5-users mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
