[openocd:tickets] Re: #406 "Failed to read memory" leads to 0 value instead of error message in gdb

That comment is more than 15 years old now. I have not noticed any problems with gdb stacktraces enabling that option. Given that with other toolchains this does not happen, this is far from intuitive and easy to note behaviour. It took quite a while to even notice that all zeroes are returned.

[PATCH]: 7a710953db libusb_helper: split error and returned value

This is an automated email from Gerrit. "Antonio Borneo " just uploaded a new patch set to Gerrit, which you can find at https://review.openocd.org/c/openocd/+/7756 -- gerrit commit 7a710953db734cc282ecf90b542c7ebb3a4dbafa Author: Antonio Borneo Date: Sun Jul 2 23:48:42 2023 +0200 libus

[openocd:tickets] Re: #406 "Failed to read memory" leads to 0 value instead of error message in gdb

> I think that this should be the default state Based on the comments here that may not be the most judicious approach: * https://github.com/openocd-org/openocd/blob/56fd04832abc0ebadc21ee6127be4be9c7b46e15/src/server/gdb_server.c#L1518 /* TODO : Here we have to lie and send b