Binary Ninja VS LLDB

If you really want to poke around in the binary, you can use a decompiler like IDA, Ghidra, or Binary Ninja's free version. Source: 6 months ago

Still $$$ for crippled functionality. As an alternative, https://binary.ninja is gaining traction at work. - Source: Hacker News / 10 months ago

As I said, a regular text editor won’t do for reading a binary file, so I needed to choose a disassembler to break the challenge binaries out into their basic blocks. I chose to use Binary Ninja because it has a very easy-to-use Python API, and it’s hobbyist-level cheap (for comparison, the industry-standard disassembler is IDA Pro, which they will sell to you for roughly an arm, and continue to pick off your... - Source: dev.to / over 3 years ago

It’s an awesome reverse engineering tool (https://binary.ninja). Has really nice api support so you can basically automate anything and make plugins for custom architectures and stuff like that. Source: almost 2 years ago

It's basically the opposite of https://godbolt.org/ -- put in binary, get out decompilation amongst many decompilers. It's open source (though you need a Binary Ninja and Hex-Rays license to run internally -- you'll want to check with the respective companies to make sure your particular license is acceptable for use even internally first!). Source: almost 2 years ago

I'm on the record of loving the VSCode experience with Rust. And I do think that it's amazing that a "non-IDE" can feel so much like an IDE. However, I've recently pivoted off of that stance. I know it's still in EAP, but Rust Rover gives me all of the things that I get from VSCode plus an easier integration with LLDB. - Source: dev.to / 3 months ago

Fortunately, we can use this same technique with our Node.js applications! This is possible through llnode: a LLDB plugin which enables us to inspect Node.js core dumps. With llnode, we can inspect objects in the memory and look at the complete backtrace of the program, including native (C++) frames and JavaScript frames. It can be used on a running Node.js application or through a core dump. - Source: dev.to / 11 months ago

The CMake-based, itk-wasm build system tooling enables the same C++ build system configuration and code to be reused when building a native system binary or a WebAssembly binary. As a result, native binary debugging tools, such as GDB, LLDB, or the Visual Studio debugger can be utilized. - Source: dev.to / about 1 year ago

The debugger component of the LLVM project. It’s what you’re typing into when you type po someExpression. https://lldb.llvm.org/ Web searches could help explain a lot of this for you 😊. Source: over 1 year ago

If you really don't want to touch Visual Studio/MSVC then you can try to compile with clang and use lldb: https://lldb.llvm.org/. Source: over 1 year ago