On 27 March 2018 at 11:13:10, Matthias Welwarsky (matthias.welwar...@sysgo.com) wrote:
> However, reporting an error to gdb doesn't seem to be all that > useful. I've > been trying with a Cortex-M target (STM32F303) and effectively > the error > prevents gdb from fetching all registers from the target. yes, this is similar to what I noticed in my tests. understanding why GDB behaves like this would be interesting, but the usefulness would be debatable; as long as existing GDBs are not able to cope with errors, openocd should not report them. probably the RISC-V GDB was patched to understand these errors. anyway, I think that the patch helps the current distributions which include the RISC-V fork, without affecting other targets, and it is simple enough to be understood. what might be needed are some more explanations, to prevent people enabling this behaviour for targets with GDBs not supporting this error processing. regards, Liviu ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
