DBDelve
Dive deep into your data. A fast, native, multi-engine database client written in Rust. Free and open source, no telemetry.
翻訳待ち
Process Explorer for MacOS
翻訳待ち
開発ツールGitHub @microsoft自分でインストール所有者未確認
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
Buzzing on social · #11 now · 2 sources
Checked 11月13日 21:16 · Scores are copied from each platform at the last check. We don’t copy post bodies or comments, and deleted posts disappear here too.
リポジトリ情報はまだ収集していません。
No updates detected yet. GitHub releases will appear here.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Sysinternals Process Explorer for Mac is a native macOS implementation of the core Process Explorer experience. It provides a live process tree, lower-pane module/handle/thread inspection, rich per-process properties, system-wide performance graphs, code-signing inspection, and macOS-specific equivalents for Process Explorer workflows.
The app is built with Swift, SwiftUI, and AppKit, with sampling backed by public macOS APIs such as libproc, sysctl, Mach host statistics, Security.framework, IOKit, Metal, and optional privileged helper support.
xcodegen for regenerating ProcexpMac.xcodeproj from project.yml.Install xcodegen if needed:
brew install xcodegen
Generate the Xcode project and build the Debug app:
xcodegen generate
xcodebuild -scheme ProcexpMac -configuration Debug build
The Debug app is written under Xcode DerivedData. On this machine the path is typically:
~/Library/Developer/Xcode/DerivedData/ProcexpMac-czqddcuyalgzfgebjezrhssregtw/Build/Products/Debug/ProcExp\ \(Dev\).app
You can also open the generated project in Xcode:
xcodegen generate
open ProcexpMac.xcodeproj
After a Debug build, launch the app with:
open "$HOME/Library/Developer/Xcode/DerivedData/ProcexpMac-czqddcuyalgzfgebjezrhssregtw/Build/Products/Debug/ProcExp (Dev).app"
If your DerivedData suffix differs, locate the product with:
find ~/Library/Developer/Xcode/DerivedData -path '*/Build/Products/Debug/ProcExp (Dev).app' -print
To relaunch a freshly built app from this workspace:
app="$HOME/Library/Developer/Xcode/DerivedData/ProcexpMac-czqddcuyalgzfgebjezrhssregtw/Build/Products/Debug/ProcExp (Dev).app"
pids=$(pgrep -f "$app/Contents/MacOS/ProcexpMac" || true)
if [[ -n "$pids" ]]; then kill $pids 2>/dev/null || true; fi
open -n "$app"
Unqualified Xcode and local ad-hoc builds use ProcExp (Dev).app with bundle
ID com.sysinternals.procexpmac.dev. Its helper uses the separate launchd and
Mach service ID com.sysinternals.procexpmac.dev.helper. The development app,
helper approval, preferences, and LaunchServices registration therefore do not
replace an installed official copy.
The official identities are reserved for an explicit Developer ID build or the
Azure release pipeline: ProcExp.app, com.sysinternals.procexpmac, and
com.sysinternals.procexpmac.helper. The build and signing scripts validate the
entire tuple before signing or publishing it.
Run the full Swift package test suite:
swift test
Run the live smoke test:
swift run ProcexpSmoke
Run focused test suites:
swift test --filter ProcexpModelTests
swift test --filter ProcexpNetworkTests
swift test --filter ProcexpSigningTests
The repository includes a small stateful TCP fixture for testing the TCP/IP tab:
swift build --product ProcexpTcpFixture
.build/debug/ProcexpTcpFixture --duration 3600 --remote-host github.com --remote-port 22
The fixture opens a loopback listener, creates a loopback established connection, and optionally opens a DNS-resolved remote TCP connection. Select the fixture process in Process Explorer and open Properties > TCP/IP to inspect the sockets and remote-name resolution.
This is the beginning of the README. Read the rest at the original. Read the full README ↗