0.9.5 is now available for Windows and Linux.
macOS is missing for now which wasn't really intended and I will try to fix this within the upcoming days. At the moment the only working build is signed but can't be notarized by current standards. Meaning that running it when flagged "com.apple.quarantine" may be harder but I have to check that. Unfortunately I can't get the task_for_pid entitlement to work when signing and notarizing with the correct options. macOS then fails to check the signature on startup (thereby forcefully killing it) even when it is perfectly valid from what I see. If there is someone here who may be able to give insight into this I am happy for any help.
This release is labeled as beta, meaning that chances are good that it will work for small to medium sized projects rather well.
Support for unlinked debug information like fastlink should be considered experimental, however that code is passing the same tests as everything else so there is a good chance it will work.
If anything doesn't work please don't hesitate to contact so that your issues can be fixed for the next upcoming update or a smaller fix if applicable. While most basic functionality in codeclap is tested via automated tests, some features aren't that easy to be tested outside the actual interface and it is also hard to keep track of all of them by hand. There have been quite a lot of changes (for example rendering on Windows is now fully D3D11, Metal on macOS and OpenGL 3 on Linux) and it is easy to break something for individual use cases.
The full changelog is available here: https://issues.codeclap.cc/changelog_page.php?version_id=15
Known issues and planned features: https://issues.codeclap.cc/roadmap_page.php?version_id=3
So what's up next.
Cleanup and bugfixes
The focus of codeclap in regards to support for different operating systems and formats has shifted quite a bit since the initial incarnation. For the next update one big focus is to unify the handling of different platforms as much as possible to avoid breaking individual platforms. Adding another variable (x64/ARM architectures) makes this even more important.
Currently codeclap works well when navigating in few files at a time and jumping between functions (using "jump to any") while debugging. However keeping track of a lot of open files and the directory structure within the "project" (as a term for the binary that is executed and all linked debug information and source files) isn't very comfortable. 0.9.8 should support this better by providing a "project explorer" like the one in every IDE.
There are also definitely a few usability issues remaining and I will keep an eye on how to make codeclap as easy to use as possible.
Support for other architectures
If nothing goes wrong codeclap will become capable of supporting additional architectures besides x64. I will start with this rather soon by porting to ARM64/AArch64 on Linux. The goal after that is to provide support for ARM-based macOS as soon as possible (which is the main reason to start working on this now).
Free evaluation version
There will be a free evaluation version at some point after 1.0. However it is not yet clear in which way this version will be different from the full "pay to use" release. If you are unsure if codeclap will reach a point where it is really worth the price for you I'd highly encourage you to wait for the free version, try it out and then decide. However if you basically can't wait to try out every single update and want to support this project and its goals then you are at the right place. Of course there is a large space in between these two sides and there you just have to decide for yourself.
Happy coding and stay safe