Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • For a few years now, I routinely run Emacs through gdb on OSX 10.6.8 and through lldb on El Capitan so that I can catch any crash when it happens. Who do you believe it is "tricky" to accomplish on your version of MacOS? For lldb, my notes indicate that I had to give permission with DevToolsSecurity -enable and that gave me a confirmation of "Developer mode is now enabled."..., but again that was on El Capitan. For OSX 10.6.8, I run ggdb from MacPorts instead of the built-in gdb. I have some notes regarding code-signing for ggdb on El Capitan, .... Commented Aug 26, 2020 at 21:52
  • My suggestion would be to bite the bullet by spending the time to get gdb working on your version of MacOS, build Emacs from source, and launch the binary from the src directory so that the .gdbinit is read ... Then, the Emacs developers can help you debug and perhaps even fix the problem. I spent quite a bit of time getting a newer version of gdb installed on my outdated version of Windows just so that I could obtain help from those Emacs developers who needed a specific debugging readout only available in newer versions of gdb .... Commented Aug 26, 2020 at 22:00