Re: [gem5-dev] Remote GDB with Multiple Instruction Widths?

2019-08-18 Thread Alec Roelke
Well, I'm not looking for the behavior of GDB itself, since I can infer that from RISC-V OpenOCD's code; I'm looking for how gem5 responds to GDB requests. I did find what I was looking for in x86's implementation of remote_gdb, though. It turns out it overrides checkBpLen, which didn't occur to

Re: [gem5-dev] Remote GDB with Multiple Instruction Widths?

2019-08-12 Thread Gabe Black
In x86, a software breakpoint is generally only one byte, the int3 instruction which is defined for that purpose. It's put at the start of whatever instruction you want to catch. In other ISAs like ARM which have different instruction sizes, I'm assuming gdb either figures out what the size of the

[gem5-dev] Remote GDB with Multiple Instruction Widths?

2019-08-10 Thread Alec Roelke
I'm trying to fix the remote connection to GDB in RISC-V (patch #20028 ) and I'm running into an issue where RISC-V GDB is sending a breakpoint of length 2 bytes, but gem5 is expecting one of length 4 (the length of an instruction, see lin