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

FSEM[ERROR]: Function 0x00000940 has no out edges. #19

Closed
lcytxw opened this issue Jul 25, 2019 · 1 comment
Closed

FSEM[ERROR]: Function 0x00000940 has no out edges. #19

lcytxw opened this issue Jul 25, 2019 · 1 comment

Comments

@lcytxw
Copy link

lcytxw commented Jul 25, 2019

I got such error when I run the testcase ooex5.cpp from dir pharos/src, any suggestions would be greatly appreciated.

icy@ubuntu:~/cpp_test$ ooanalyzer --json ooex5.json ./ooex5 --allow-64bit
OPTI[INFO ]: Analyzing executable: ./ooex5
OPTI[INFO ]: OOAnalyzer version 0.13.
OPTI[INFO ]: ROSE stock partitioning took 0.687482 seconds.
OPTI[INFO ]: Long delays until the next time stamp are caused by the Pharos custom partitioning
OPTI[INFO ]: algorithm and may be resolved by using the --stockpart option, but at the expense
OPTI[INFO ]: of possibly less complete function detection. Using --no-semantics may also help.
OPTI[INFO ]: Function partitioning took 0.829896 seconds.
FSEM[ERROR]: Function 0x00000940 has no out edges.
OPTI[ERROR]: bad operand size found @ 0x000009D3 : 0
OPTI[ERROR]: bad operand size found @ 0x00000D19 : 0
OOAN[ERROR]: No new() methods were found. Heap objects may not be detected.
OOAN[ERROR]: No delete() methods were found. Object analysis may be impaired.
OPTI[INFO ]: Function analysis complete, analyzed 36 functions in 0.354419 seconds.
OPTI[ERROR]: No C++ classes were detected in the program.
OPTI[INFO ]: OOAnalyzer analysis complete.

@cfcohen
Copy link

cfcohen commented Jul 25, 2019

OOAnalyzer only supports 32-bit Windows executables at the present time. Because your test executable does not have a .exe extension, I presume that you're testing against a Linux executable built from the recently published source code. The reasons that OOAnalyzer does not presently support Linux executables or 64-bit Windows executables is a bit complicated, but some folks are currently working on fixing that.

@lcytxw lcytxw closed this as completed Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants