dnSpyEx vs OpenOCD

dnSpyEx is an unofficial continuation of dnSpy, a debugger and .NET assembly editor for working with assemblies without source code. It can debug .NET Framework, .NET, and Unity game assemblies, with breakpoints, tracepoints, conditional breakpoints, exception breakpoints, and multiple-process debugging. Editing covers metadata and methods or classes in C# and Visual Basic, plus low-level IL method bodies. The project lists C# and Visual Basic decompilers using the ILSpy engine, along with a BAML decompiler and disassembler. Assembly search, class and method usage analysis, caller finding, bookmarks, and project export are also included. A public API supports extensions, and the C# Interactive window can control or script dnSpyEx. The latest stable release listed is v6.6.0, which adds a .NET 10 distribution. It is free under GPLv3. Release notes describe Wine compatibility adjustments for Linux, not native Linux support. Dynamic methods cannot be debugged because of CLR limitations.

OpenOCD provides debugging, in-system programming, and boundary-scan testing for embedded target devices through a debug adapter. It communicates with targets over JTAG or Serial Wire Debug (SWD), and can run as a server for GDB clients. Users can also interact through Telnet or GDB; its Tcl interface is intended for machine interaction, and configuration files can contain commands using the documented Tcl scripting API. The target list includes ARM, MIPS, RISC-V, Xtensa, ARC, AVR32, and other architectures. Release 0.12.0 notes support for Espressif ESP32, ESP32-S2, ESP32-S3 cores, and Raspberry Pi Pico RP2040, along with Zephyr and a no-RTOS option. OpenOCD supports remote debugging and exception breakpoints. It is free and listed for Linux, macOS, Windows, and self-hosted setups. The project says it is packaged in popular operating-system repositories and provides access to source code; community binaries are marked unofficial. Host configuration may take extra steps: Linux usually needs a udev rule for adapter access, and Windows requires driver configuration for each peripheral.