![[Linux]](http://worker.jart.workers.dev/redbean/linux.png "Linux"){kind=small}
![[Windows]](http://worker.jart.workers.dev/redbean/windows10.png "Windows"){kind=small}
![[MacOS]](http://worker.jart.workers.dev/redbean/macos.png "MacOS"){kind=small}
![[FreeBSD]](http://worker.jart.workers.dev/redbean/freebsd64.png "FreeBSD"){kind=small}
![[OpenBSD]](http://worker.jart.workers.dev/redbean/openbsd.png "OpenBSD"){kind=small}
![[NetBSD]](http://worker.jart.workers.dev/redbean/netbsd2.png "NetBSD"){kind=small}
memzoom-2022-07-05.com
80k - PE+ELF+MachO+ZIP+SH executable
memzoom-2022-07-05.com.dbg
1.2m - ELF debug symbols and DWARF data (optional)
curl https://justine.lol/memzoom/memzoom-latest.com >memzoom.com chmod +x memzoom.com ./memzoom.com -h # show help ./memzoom.com filename # view binary file ./memzoom.com -p $(pidof htop) # view process memory
If your terminal uses a white or light-colored background (instead of
black) then pass the -w flag.
Memzoom relies on the /proc filesystem to view the memory
of active processes, which may require sudo access. If your system
doesn't have /proc you can still view binary files.
If you get an error like "unable to find an interpreter" or "err:module:import_dll Library" then your system has likely been tuned to use binfmt-misc. You can safely restore the default Linux behavior for just Actually Portable Executables by running the following command:
sudo sh -c "echo ':APE:M::MZqFpD::/bin/sh:' >/proc/sys/fs/binfmt_misc/register"
You may need to run:
bash memzoom.com -hInstead of:
./memzoom.com -hThis only applies to the first invocation, after which the executable header is patched to have the MachO magic number. It's needed because the recently introduced zsh shell has backwards compatibility issues with UNIX.
You may need to run:
memzoom.com -hInstead of:
./memzoom.com -h