You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to me that commit 46f1ac6 introduced a bug. The function stlink_probe.read_memory_block8 will return an array with two bytes in it if the addressed is aligned on a 2-byte boundary but a read of 1 byte (size=1) is requested. This ends up causing an assertion at /memory.py(263)read_memory_block8(): 0107462 E Unhandled exception in handle_message (b'v'): result size (2) != requested size (1) [gdbserver]
I assume we need to add something along the lines of array[0] somewhere, though I am not sure about the appropriate place.
Thanks for the detailed report! (And very sorry it took a long time.) Fortunately, it looks like this was fixed in #1428 and released in v0.34.1. If you still have a problem, please reopen this issue.
It seems to me that commit 46f1ac6 introduced a bug. The function stlink_probe.read_memory_block8 will return an array with two bytes in it if the addressed is aligned on a 2-byte boundary but a read of 1 byte (size=1) is requested. This ends up causing an assertion at
/memory.py(263)read_memory_block8()
:0107462 E Unhandled exception in handle_message (b'v'): result size (2) != requested size (1) [gdbserver]
I assume we need to add something along the lines of
array[0]
somewhere, though I am not sure about the appropriate place.@flit
The text was updated successfully, but these errors were encountered: