Display information about files in different file formats and find gadgets to build rop chains for different architectures (x86/x86_64, ARM/ARM64, MIPS, PowerPC, SPARC64). For disassembly ropper uses the awesome Capstone Framework.
I observed that the --single option in ropper does not effectively limit the process to a single instance. Despite using this option, multiple processes are visible in tools like htop. Additionally, the memory usage appears to be abnormal, as it exhausts all available system memory, leading to an Out-of-Memory (OOM) termination. The issue is particularly pronounced when loading from cache with a 16MB coredump file and a 22MB cache.
It's important to note that the problem did not occur initially when the cache was not available. The abnormal memory consumption seem to be related to the introduction of caching. Any insights or solutions to address this memory usage anomaly would be greatly appreciated.
➜ DSM5.2 DS5615xs file core.25661
core.25661: ELF 32-bit LSB core file, Intel 80386, version 1 (SYSV), SVR4-style, from '/usr/syno/bin/findhostd', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/syno/bin/findhostd', platform: 'i686'
sashs
commented
1 year ago
I observed that the
--singleoption in ropper does not effectively limit the process to a single instance. Despite using this option, multiple processes are visible in tools like htop. Additionally, the memory usage appears to be abnormal, as it exhausts all available system memory, leading to an Out-of-Memory (OOM) termination. The issue is particularly pronounced when loading from cache with a 16MB coredump file and a 22MB cache. It's important to note that the problem did not occur initially when the cache was not available. The abnormal memory consumption seem to be related to the introduction of caching. Any insights or solutions to address this memory usage anomaly would be greatly appreciated.core.zip