Releases: Marus/cortex-debug
V1.13.0-pre6
See CHANGELOG Especially if you are using the advanced decoder.
This is a private build that has not been released to the VSCode marketplace, even as a pre-release. It is intended to test specific issues that have been addressed in the last few months.
Advance decoders for RTT now support dispose(). Also, SWO/RTT channels are recycled. See CHANGELOG.
Download the VSIX file and install it. Do NOT double-click on the vsix file. Google for instructions on how to install VSIX files in VSCode.
V1.13.0-pre5
See CHANGELOG Especially if you are using the advanced decoder.
This is a private build that has not been released to the VSCode marketplace, even as a pre-release. It is intended to test specific issues that have been addressed in the last few months.
In this release, there have been a LOT of changes to how SWO is initialized via GDB. I do not have every probe available to me so I tested with the ones I had, mainly with STLink and OpenOCD. Any feedback is welcome.
Download the VSIX file and install it. Do NOT double-click on the vsix file. Google for instructions on how to install VSIX files in VSCode.
V1.13.0-pre4
See CHANGELOG
This is a private build and not released to the VSCode marketplace even as a pre-release. This is intended to test specific issues that have been addressed in the last few months.
SWO seems to be broken if a connection is not established with the server in under a second. Sorry
Download the VSIX file and install it. Do NOT double-click on the vsix file. Google for instructions on how to install VSIX files in VSCode.
V1.13.0-pre3
Contributors
Assets 3
V1.13.0-pre2
See CHANGELOG
Download the VSIX file and install it. Do NOT double-click on the vsix file. Google for instructions on how to install VSIX files in VSCode.
V1.12.1-pre6
Fix for Issue #929
V1.12.1-pre5
Faster stack traces using an alternate approach to querying GDB. Only helps when your stack is corrupted or too big. This can help when you are single-stepping with a corrupt stack.
Also, it does not help when your stack is so corrupted that GDB crashes or hangs on stack-trace/local-variable requests.
V1.12.1-pre3
More complete fix for #923. Was a problem with aliased locals, globals and statics as well.
Sorry, commit tag is wrong but the VSIX is correct
V1.12.1-pre2
Potential Fix for issue #923. It affects both watch and hover variables
V1.12.1-pre1
Minor changes. Now (optional) timestamps are shown even when "showDevDebugOutput" is set to "vscode" for messages generated by Microsoft.