Not sure about ClickHouse though.
[^1]: https://www.timdbg.com/posts/writing-a-debugger-from-scratch... [^2]: https://nostarch.com/building-a-debugger
--
1: https://github.com/munificent/craftinginterpreters/issues/92...
Another book added to my To-Read list
[1]:https://keowu.re/posts/Writing-a-Windows-ARM64-Debugger-for-...
I don't want to go through the curl | bash either for security reasons.
It would be nice to have some package manager support, but it looks cool.
All you need to do otherwise is add it in PATH.
> Linux only > x86 only > 64-bit only
Linux may not be so pretty, but it's far more comfortable.
edit: and a reason you would do this locally using ssh is debugging the UI layer itself. if you have to step through the window server, you can't be using the window server at the same time. Remote lldb/gdb debugging is often just flaky. I don't know why they're so unreliable, but they are.
dec0dedab0de•3h ago
Operations that can't be instantaneous (loading debug info, searching for functions and types) should be reasonably efficient, multi-threaded, asynchronous, cancellable, and have progress bars.
I wish this were more common, especially the progress bars thing.
Conscat•1h ago