debug-adapter-protocol
rr
debug-adapter-protocol | rr | |
---|---|---|
14 | 102 | |
1,325 | 8,665 | |
2.3% | 0.8% | |
7.6 | 9.6 | |
11 days ago | about 20 hours ago | |
HTML | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
debug-adapter-protocol
-
The IDEs we had 30 years ago and we lost
> There's a strange dance of IDEs coming and going, with their idiosyncracies and partial plugins.
The Language Server Protocol [1] is the best thing to happen to text editors. Any editor that speaks it gets IDE features. Now if only they'd adopt the Debug Adapter Protocol [2]...
[1] https://microsoft.github.io/language-server-protocol/
[2] https://microsoft.github.io/debug-adapter-protocol/
-
Bitty Engine: A tiny powerful game engine
Wonder if they've got support for Debug Adapter Protocol? https://microsoft.github.io/debug-adapter-protocol/
- Hi vimmers! Does any one use F[1..12] keys and what for? Cheers!
-
What a good debugger can do
> Debuggers need to do more things
It's true that coming up with an interface for an abstract debugger is harder, but it's not impossible. Microsoft create Debug Adapter Protocol (https://microsoft.github.io/debug-adapter-protocol/), which is conceptually similar for LSP. It's not perfect, but covers most basic operations pretty well, while leaving to the debugger to deal with the implementation details.
-
There is No “Tooling Issue” in Haskell
Most languages also include support for the Debug Adapter Protocol, and Haskell is no exception, so if you are so inclined, you can hook up your favorite editor/IDE and go to town.
-
Debug this meme
They're working on the Debug Adapter Protocol but it doesn't have critical mass/adoption yet. And yeah, I end up having a fair share of dbg!(foo). It's not so bad since dbg!() also returns its value, so you don't have to mess with your code too much.
-
Step Debugger Development: Debug Adapter Protocol Support
TL;DR: What would it take to implement a Debug Adapter Protocol (DAP)-based step debugger?
- DAP – Debug Adapter Protocol
-
Try TeXmacs in your Browser via WebAssembly (Mogan Fork of TeXmacs)
RDP is the Windows Remote Desktop Protocol that was in use for decades before VSCode; VSCode's own remoting doesn't use it.
I'd say that, in addition to LSP, the other big thing that came out of VSCode is DAP: https://microsoft.github.io/debug-adapter-protocol.
-
I got fired yesterday for using vim
The most important part is the JDT Languag Server, it will give you the Java tooling for writing code. I think it has DAP support as well, so with a DAP client like nvim-dap you should be able to debug as well.
rr
- rr: Lightweight Recording and Deterministic Debugging
-
Hermit is a hermetic and reproducible sandbox for running programs
I think this tool must share a lot techniques and use cases with rr. I wonder how it compares in various aspects.
https://rr-project.org/
rr "sells" as a "reversible debugger", but it obviously needs the determinism for its record and replay to work, and AFAIK it employs similar techniques regarding system call interception and serializing on a single CPU. The reversible debugger aspect is built on periodic snapshotting on top of it and replaying from those snapshots, AFAIK. They package it in a gdb compatible interface.
Hermit also lists record/replay as a motivation, although it doesn't list reversible debugging in general.
- Rr: Lightweight Recording and Deterministic Debugging
-
Deep Bug
Interesting. Perhaps you can inspect the disassembly of the function in question when using Graal and HotSpot. It is likely related to that.
Another debugging technique we use for heisenbugs is to see if `rr` [1] can reproduce it. If it can then that's great as it allows you to go back in time to debug what may have caused the bug. But `rr` is often not great for concurrency bugs since it emulates a single-core machine. Though debugging a VM is generally a nightmare. What we desperately need is a debugger that can debug both the VM and the language running on top of it. Usually it's one or the other.
> In general I’d argue you haven’t fixed a bug unless you understand why it happened and why your fix worked, which makes this frustrating, since every indication is that the bug exists within proprietary code that is out of my reach.
Were you using Oracle GraalVM? GraalVM community edition is open source, so maybe it's worth checking if it is reproducible in that.
[1]: https://github.com/rr-debugger/rr
-
So you think you want to write a deterministic hypervisor?
https://rr-project.org/ had the same problem. They use the retired conditional branch counter instead of instruction counter, and then instruction steeping until at the correct address.
-
Is Something Bugging You?
That'll work great for your Distributed QSort Incorporated startup, where the only product is a sorting algorithm.
Formal software verification is very useful. But what can be usefully formalized is rather limited, and what can be formalized correctly in practice is even more limited. That means you need to restrict your scope to something sane and useful. As a result, in the real world running thousands of tests is practically useful. (Well, it depends on what those tests are; it's easy to write 1000s of tests that either test the same thing, or only test the things that will pass and not the things that would fail.) They are especially useful if running in a mode where the unexpected happens often, as it sounds like this system can do. (It's reminiscent of rr's chaos mode -- https://rr-project.org/ linking to https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo... )
-
When "letting it crash" is not enough
The approach of check-pointing computation such that it is resumable and restartable sounds similar to a time-traveling debugger, like rr or WinDbg:
https://rr-project.org/
https://learn.microsoft.com/windows-hardware/drivers/debugge...
- When I got started I debugged using printf() today I debug with print()
- Rr: Record and Replay Debugger – Reverse Debugger
-
OpenBSD KDE Plasma Desktop
https://github.com/rr-debugger/rr?tab=readme-ov-file#system-...
What are some alternatives?
cortex-debug - Visual Studio Code extension for enhancing debug capabilities for Cortex-M Microcontrollers
CodeLLDB - A native debugger extension for VSCode based on LLDB
ghci-dap - ghci having DAP interface.
rrweb - record and replay the web
flow-storm-debugger - A debugger for Clojure and ClojureScript with some unique features.
gef - GEF (GDB Enhanced Features) - a modern experience for GDB with advanced debugging capabilities for exploit devs & reverse engineers on Linux
error-message-index - A community-driven collection of documentation for Haskell error messages and warnings
Module Linker - browse modules by clicking directly on "import" statements on GitHub
watchpoints - watchpoints is an easy-to-use, intuitive variable/object monitor tool for python that behaves similar to watchpoints in gdb.
nbdev - Create delightful software with Jupyter Notebooks
mogan - Mogan (based on GNU TeXmacs): Let us enjoy exploring science and technology!
clog-cli - Generate beautiful changelogs from your Git commit history