I have an impression that each version of macOS system introduces additional obstacles for developer. From one point of view I understand that they just want to make the system more secure, and that should be the biggest priority above all (well, maybe not above common sense). But it's hard to accept the fact that i.e. Valgrind doesn't work anymore, tools like lldb don't work out of the box, etc.
To be able to use lldb on Mojave and probably above, you need to enable developer mode. So, if you get this:
Open callgrind files on macOS with Profiling Viewer. It supports Callgraph, Treemap, Heatmap, Call tree. You can export PDF reports. It handles multiple types of costs (eg. Time and Memory) and positions. 在 configure 文件中，valgrind的注释提到在MacOS下会同时编译i386和x8664，这是问题的根本原因，或者说valgrind在Mojave下编译的坑。幸好 configure 提供了只编译64位的选项，不需要修改 configure 文件。 总结一下，你要做的是. The official version of Valgrind doesn't support 10.14 either, and I don't have a 10.14 system to test with. What I'm seeing is the following (this is the Valgrind opcode dump, not the execution sequence). So my next step was to run on both Mojave and Catalina with -trace-syscalls=yes. It looks like the one that is failing on Catalina is a. Hello Valgrind Community, I'm a student working in IT at The University of Chicago, and our team has been tasked with updating our Mac lab machines to Mac OS Mojave. Some of our professors teach Valgrind in various courses as a useful debugging tool to help students catch memory bugs in their programs - I myself have benefited greatly from its use. Valgrind on Mojave using Docker 2019-11-29 Valgrind is a very useful tool that allows you to spot memory leaks, memory corruptions and other bugs in your program which would have otherwise been difficult to find and track down.
try doing this:
After enabling 'developer mode', lldb should work again:
本文是给想在Mojave上编译安装valgrind的人一个参考。
个人因为《Hands on concurrency with Rust》这本书的原因，需要安装valgrind。但是现在（2019/2/9）稳定版本的valgrind尚未支持Mojave，即不能通过Homebrew安装。valgrind的bug tracker里有这个问题的追踪， 但是看状态估计离正式发布还需要时间（开源项目常有的事情，缺少资源，哎）。对话中给了一个github上的commit，看起来可以使用。
下载对应的repository，checkout到修改版的branch上
2 4 6 8 10 | Primary build arch: amd64 Build OS: darwin Primary build target: AMD64_DARWIN Platform variant: vanilla Primary -DVGPV string: -DVGPV_amd64_darwin_vanilla=1 Default supp files: exp-sgcheck.supp xfree-3.supp xfree-4.supp darwin10-drd.supp darwin18.supp |
假如Secondary build arch不像上面那样为空的话，比如是i386，那么make时会出现以上问题。
在 configure 文件中，valgrind的注释提到在MacOS下会同时编译i386和x86_64，这是问题的根本原因，或者说valgrind在Mojave下编译的坑。幸好 configure 提供了只编译64位的选项，不需要修改 configure 文件。
总结一下，你要做的是
小结
老实说很后悔升级到了Mojave，MacBook的睡死，突然mic不能使用等问题，现在又来一个valgrind……
See Full List On Github.com
不管怎么说，希望本文对你有所帮助。