LLDB vs Ruby debug

LLDB is a free debugger built from reusable components that use LLVM libraries, including Clang's expression parser and the LLVM disassembler. It is the default debugger in Xcode on macOS and supports debugging C, C++, and Objective-C on desktop and iOS devices and simulators. Its tools include breakpoints, watchpoints, process launching, and attaching to programs; remote debugging is also documented for Linux, Windows, Android, and iOS. Expression evaluation uses Clang infrastructure for current C-family language features, multiline expressions, and just-in-time evaluation where supported. Developers can use its shared-library C++ API and Python bindings for scripting, symbolication, disassembly, and inspecting object and symbol files. The lldb-dap adapter connects LLDB functionality to compatible editors and IDEs, including Visual Studio Code, Emacs, vim, and neovim. LLDB is available under the Apache 2.0 License with LLVM exceptions. Windows support remains under active development, with ARM and AArch64 described as more experimental. The lldb-dap interface documents no support for step-back, setting a variable, goto-target, or terminate requests.

Ruby debug is a free, BSD-2-Clause open-source debugger for Ruby MRI 2.7 and later, delivered for Linux and self-hosted use. Its console evaluates Ruby expressions, inspects program state, controls execution, sets conditional and exception breakpoints, and enables tracing. The debugger can record execution and replay it by stepping backward through the log. Remote sessions work over UNIX domain sockets or TCP/IP, allowing a console to attach to a running program. An IRB console adds autocompletion, multiline input, and commands including `show_source` and `show_doc`. The `rdbg` command launches Ruby scripts and commands such as Rails, Rake, and RSpec under debugging. Frontends are described for VS Code and Chrome DevTools; VS Code requires the vscode-rdbg extension. Installation uses `gem install debug` or a Gemfile entry. The project reports no performance penalty when not stepping and with no breakpoints set. It warns that remote messages are unencrypted and that `debug/open_nonstop` can expose access without stopping the program.