chromedp vs MemDBG

chromedp is a Go package for driving browsers that support the Chrome DevTools Protocol without an external driver. It runs Chrome headlessly by default and supports actions such as navigating, clicking, reading page text, running JavaScript, filling forms, and waiting for elements. Its examples also cover cookies, HTTP headers, proxy authentication, request interception, session restoration, and HAR recording. For output, it can capture screenshots, print pages to PDF, and save screencast frames as JPEG files. Separate browser contexts can support parallel work, but sharing one context between goroutines can cause races. A separate remote module connects to an already-running browser over WebSocket, and the project provides a headless-shell Docker image. By default, Chrome communicates over remote-debugging pipes and does not open a debugging port; switching to WebSocket uses one. The package is available under the MIT license at free. The README requires Go 1.27 or newer.

MemDBG is a console payload and native frontend for memory inspection, scanning, debugging, trainer creation and research on PS4, PS5 and host machines. Its stated uses include offline homebrew development, reverse-engineering education, preservation and authorized security research. Scan workflows include exact values, process-wide searches, AOB patterns, pointer chains, unknown values and heuristic Smart Auto-Search. Debugging tools cover thread control, stepping, registers, breakpoints, watchpoints, stack walking and disassembly. Trainer workflows support .cht save and load, batchcode import, ON/OFF values, lock intervals and patch-to-trainer export. The frontend supports desktop-side Lua and Python plugins from repository manifests, with a public MemDBG plugin repository as its default source. It documents a GDB remote bridge for IDA Pro and an optional x64dbg plugin bridge. MemDBG is free and licensed GPL-3.0-or-later; it is in active pre-release development. Host builds bind to loopback by default, and the project recommends an allowlisted frontend IP for LAN sessions. Some macOS debugger actions may need SIP or code-signing changes; the iOS/iPadOS release artifact is unsigned.