Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issue when analyzing inputs with arch specified with evm #12510

Open
hongxuchen opened this issue Dec 18, 2018 · 1 comment
Open

Comments

@hongxuchen
Copy link

hongxuchen commented Dec 18, 2018

Questions Answers
OS/arch/bits (mandatory) Ubuntu x86 64
File format of the file you reverse (mandatory) -
Architecture/bits of the file (mandatory) -
r2 -v full output, not truncated (mandatory) radare2 3.2.0-git 20447 @ linux-x86-64 git.3.1.3-98-gd2133cbdf commit: d2133cb build: 2018-12-18__16:17:40

Expected behavior

r2 analyzes and exits.

Actual behavior

r2 takes quite a long time to analyze and exit.

Steps to reproduce the behavior

  • build radare2 (./sys/install.sh)
  • r2pm install evm
  • run time r2 -a evm -AA -Q $FILE. It may take quite a lot of time during Emulate code to find computed references (aae) the procedure, on one of my machines it took almost 1 hour on one of the seeds; on the other hand, when no arch is specified, time r2 -AA -Q $FILE exits immediately. The uploaded archive contains the sample input files.
    hangs.zip

Additional Logs, screenshots, source-code, configuration dump, ...

  • r2pm version 3.2.0-git
  • radare2-extras version 7436fe3.
@stale
Copy link

stale bot commented Nov 18, 2020

This issue has been automatically marked as stale because it has not had recent activity. Considering a lot has changed since its creation, we kindly ask you to check again if the issue you reported is still relevant in the current version of radare2. If it is, update this issue with a comment, otherwise it will be automatically closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 18, 2020
@trufae trufae removed the bug label Jun 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants