Normally to debug program you would just run dtruss program and look at the output.

dtruss itself is just a script using the powerful DTrace framework, but if dtruss does what you need it’s a lot easier to use than writing your own DTrace script. If you just want to fix this problem skip to the end, or read on for how I found the solution.Ī great tool for debugging all sorts of problems on Mac OS X is dtruss, which prints out details of the system calls a program makes. However on Mac OS X something has changed (I’m not sure exactly what) that results in mc 4.8.14 taking about 10 seconds to start. It’s widely available, is text based so works over SSH, it’s quite capable, and it’s very fast. I sometimes use Midnight Commander (mc) as a file manager.

Every other brew app seems to work fine.īrew doctor Your system is ready to brew.īrew config HOMEBREW_VERSION: 3.0.0 ORIGIN: HEAD: ebc7cc36a0e029d58fac8cebd1b5ff583b3fd95b Last commit: 6 days ago Core tap ORIGIN: Core tap HEAD: d1696e62cc1740dd955566dc79a12ac2fbd70e6c Core tap last commit: 2 hours ago Core tap branch: master HOMEBREW_PREFIX: /opt/homebrew HOMEBREW_CASK_OPTS: HOMEBREW_MAKE_JOBS: 8 Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/amework/Versions/2.6/usr/bin/ruby CPU: octa-core 64-bit arm_firestorm_icestorm Clang: 12.0 build 1200 Git: 2.30.1 => /opt/homebrew/bin/git Curl: 7.64.1 => /usr/bin/curl macOS: 11.2-arm64 CLT: 12.15 Xcode: N/A Rosetta 2: falseīeta Was this translation helpful? Give feedback.Fixing slow startup of mc on Mac OS X using dtruss Yes, i had the problems mentioned here ( Homebrew/brew#10275) but everything seems to be fixed after uninstalling/installing/reinstalling (with cleanup) xcode and git. Uninstall, Install, Reinstall, Update, upgrade doesnt help.

Everytime i try to start mc it got immediately killed.

Midnight commander macos