How momo5502/sogen works
Sogen executes Windows and Linux binaries by emulating CPU instructions and operating-system syscall behavior, with selectable CPU backends. The main workflow is to submit a program through the web playground or a native analyzer, run it in the relevant OS emulator, and inspect or control execution through hooks and debugger interfaces. Major supporting capabilities include module loading, memory management, state snapshots, Python bindings, and managed subprocesses. Several subsystem links below are documented in the README; unsampled implementation details are not treated as verified call paths.
Main entry points: windows_emulator.hpp Windows emulator · linux_emulator.cpp Linux emulator · main.cpp Windows analyzer · App.tsx Web app
Components 22
Web experience
- Web app
page/src/App.tsx - Landing page
page/src/landing-page.tsx - Emulation playground
page/src/playground.tsx - Emulator worker
page/public/emulator-worker.js
Execution runtime
- CPU backends
src/backend-selection/backend_selection.cpp - Binary module loading
src/windows-emulator/module/module_manager.cpp - Windows memory
src/windows-emulator/memory_manager.cpp - Linux memory
src/linux-emulator/linux_memory_manager.cpp - State snapshots
src/emulator/serialization.hpp
Guest operating systems
- Windows emulator
src/windows-emulator/windows_emulator.hpp - Linux emulator
src/linux-emulator/linux_emulator.cpp - Windows services
src/windows-emulator/syscall_dispatcher.cpp - Linux syscalls
src/linux-emulator/linux_syscall_dispatcher.cpp - Guest filesystem
src/windows-emulator/file_system.hpp - Windows registry
src/windows-emulator/registry/registry_manager.cpp
Inspection and control
- Debugger event handling
src/debugger/event_handler.cpp - GDB protocol
src/gdb-stub/connection_handler.cpp
External interfaces
- Windows analyzer
src/windows-analyzer/main.cpp - Linux analyzer
src/linux-analyzer/main.cpp - Python bindings
src/python-bindings/sogen_module.cpp - Managed processes
src/process-manager/subprocess_process_manager.cpp
Other components
- Program user
Connections 26
- Program user → Web app: opens
page/src/App.tsx - Web app → Landing page: routes to
page/src/App.tsx - Web app → Emulation playground: routes to
page/src/App.tsx - Emulation playground → Emulator worker: dispatches work
- Program user → Windows analyzer: starts program
README.md - Program user → Linux analyzer: starts program
- Windows analyzer → Windows emulator: sets up
src/windows-analyzer/main.cpp - Windows analyzer → Managed processes: uses managed process
src/windows-analyzer/main.cpp - Windows analyzer → Debugger event handling: hooks execution
- Linux analyzer → Linux emulator: runs in
- Windows emulator → CPU backends: executes with
README.md - Linux emulator → CPU backends: executes with
README.md - Windows emulator → Binary module loading: loads PE modules
src/windows-emulator/module/module_manager.cpp - Windows emulator → Windows memory: manages guest memory
src/windows-emulator/windows_emulator.hpp - Linux emulator → Linux memory: manages guest memory
- Windows emulator → Windows services: dispatches syscalls
- Linux emulator → Linux syscalls: dispatches syscalls
- Windows emulator → Guest filesystem: uses filesystem
src/windows-emulator/windows_emulator.hpp - Windows emulator → Windows registry: uses registry
- Program user → Debugger event handling: inspects execution
README.md - Debugger event handling → Windows emulator: controls emulator
src/debugger/event_handler.cpp - Program user → GDB protocol: connects debugger
README.md - GDB protocol → Windows emulator: debugs externally
- Windows emulator → State snapshots: snapshots state
README.md - Program user → Python bindings: drives runtime
README.md - Python bindings → Windows emulator: creates application
README.md