So after looking through issues, it appears the issue was patched a little bit after 8.2.1 was released which was December 2018. Next up was to go bleeding edge… yep no dice, that didn’t even compile So compiling from source using the latest 8.2.1 which at the time was the most recent release was my next step, and like Homebrew it also failed (which makes sense as that’s the same source they would be using). This isn’t Homebrew fault, rather an issue with upstream. When trying to actually run within gdb, lot’s of Googling and much head scratching it appears, that the version of source that Homebrew is using has a couple of bugs in it. Hopefully, this will get fixed, but installing from Homebrew and even after code signing it (more on that later) resulted in the error: During startup program terminated with signal SIGTRAP, Trace/breakpoint trap Well that certainly gets you a binary… not a working binary at least not today (Late April 2019) Compiling from (the right) source
MACOS MOJAVE STUCK AT LOGIN INSTALL
Indeed its as close to “official” debugger as you can get for Rust to the point the official install of rust has a rust-gdb wrapper to prettify the output.
![macos mojave stuck at login macos mojave stuck at login](https://www.howtoisolve.com/wp-content/uploads/2018/07/3-Download-Problem-Fixed-on-MacOS-Mojave-301x250.jpg)
If you’re a PHP developer you reach out for Xdebug for example or it’s even built into some languages like recent versions of Python.įor many languages, the tool to reach to is gdb (GNU Project Debugger) it supports a wide range of languages including C++ and in my case Rust. There comes a time when you want to step through your code, and breakpoints become useful. Getting gdb to (semi) reliably work on Mojave MacOS Consulting Articles Newsletter Security Talks.