4 ms·
Wow this is seriously cool. Took a while of going through it and the links to Unicorn to understand what it was (your top level comment wasn't up yet). I think
by koolba 11y ago
Wow this is seriously cool. Took a while of going through it and the links to Unicorn to understand what it was (your top level comment wasn't up yet).
I think this snippet from your Examples section sums it up best:
usercorn bins/x86.linux.elf
usercorn bins/x86_64.linux.elf
usercorn bins/x86.darwin.macho
usercorn bins/x86_64.darwin.macho
usercorn bins/x86.linux.cgc
usercorn bins/mipsel.linux.elf
- lunixbochs 11y agoThat only explains the qemu-user part. The ability to run binaries in Usercorn is just a means to an end - I want to build tools in the vein of `maybe` (VFS layer will make this easy, and so much safer), `imgtrace`, `strace`, and some stuff that's 1000x more ambitious than these. Running binaries is just... I'm recreating the universe so I can change just a few things, like logging memory access or doing taint analysis. This is similar to tools like DynamoRIO, DrMemory, PIN, valgrind, but it not only covers all of those spaces, I could probably spend a few hours listing interesting stuff outside those scopes I want to build on Usercorn (for example, you could ignore the CPU emulation part of of Usercorn and use just the kernel emulation interface to implement the Linuxulator or Windows10+Linux compat layer natively for an OS). I'll probably write real docs sometime after a proper API, but both are lower priority than core features atm.