Tommy Murphy

This issue/discussion might also be relevant here. * https://github.com/riscv-collab/riscv-gnu-toolchain/issues/1262

> This is a bit too confusing for me. :-( For me too! :-| > Do I have to adjust something in the multilib definition in my scripts? I'm not...

And we haven't even touched on proprietary extensions here yet! :-D For example: * https://github.com/riscv-collab/riscv-gnu-toolchain/issues/1261

> You mean to make it include Zicsr? Yes - on the basis that, as far as I know and have experienced, most or all RISC-V targets will require CSR...

Might be worth noting this: * https://github.com/lowRISC/lowrisc-chip/issues/209#issuecomment-1662708864 > This repository is not maintained for some while. It would be possible to get it going again, but you might prefer this...

Thanks for the reply Palmer. Perhaps you could post links (to the relevant gdb info and RISC-V gdb port review) if you get a chance? Thanks a lot.

Thanks a lot.

Anybody know if there's been any update/change in the status of gdbserver for RISC-V? If it's still not ported/working then how are people managing to debug RISC-V Linux apps with...

Thanks Jim I assumed (and hoped) that somebody was using and maybe working on gdbserver. Doesn't sound like it unfortunately.

Thanks sorear - so it sounds like proper/adequate RISC-V linux app debug support may be a long way off at the moment if people are forced to use printf "debugging"...