d-millar

@DAMisener Well, I've added some code to the script to handle the "brew unpack" issue which causes 16.0.6 to go unrecognized. Surprisingly, the sed issue is actually more complicated. I...

@cyberkaida Much appreciated - I think we're in reasonable shape right now. I made a few changes to change the default version to 16 and to handle some brew oddities,...

Yep, I think you're correct - my bash shell skills are apparently a little sketchy. Thanks!

@Alex-Vasile Apologies for not updating the script to 17 - my fault entirely. I upgraded the SWIG and forgot about the script. On the good new front, we're making changes...

Should be in the next release - @nsadeveloper789's working on the documentation as we speak.

Just to clarify, you downloaded the link labelled "Source code (tar.gz)" but not link labelled "ghidra_10.4_PUBLIC_20230928.zip"? If so, you probably (?) should have used the other link: [https://github.com/NationalSecurityAgency/ghidra/releases/download/Ghidra_10.4_build/ghidra_10.4_PUBLIC_20230928.zip] The second...

@alexandersohn Thanks for supplying the GDB log - that is incredibly helpful! @nsadeveloper789 may have other thoughts, but am pretty sure the trace is not getting started. Only the Objects...

@alexandersohn What’s in your Modules window, if anything? You may have to map your executable by hand if the Modules window is empty or no module matches your program name.

@nsadeveloper789 may have a different opinion, but, off the top of my head, I would say that only matters if you have regions of memory that would trigger a fault...

@mitchcapper Thanks for the PR, although I may put this on hold. The current Frida config was experimental at best and difficult to use in a productive way. Also, there...