You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that there are some inaccuracies in dynamo block size, to my best knowledge the block in dynamo rio always terminated with jmp or return ... which isn't the case for r2 ... that isn't the problem the real problem is that DynamoRIO calculates the sizes of blocks in wrong way which leads to graphs as the following one:
The text was updated successfully, but these errors were encountered:
a solution would be to let the user do 1 of 2 things:
A- trust DynamoRIO results and use them as is, this will lead to the problem above ..
B- use r2 sizes and keep covering blocks until you are met with ret, conditional jump or something that doesn't return.
The problem is that there are some inaccuracies in dynamo block size, to my best knowledge the block in dynamo rio always terminated with jmp or return ... which isn't the case for r2 ... that isn't the problem the real problem is that DynamoRIO calculates the sizes of blocks in wrong way which leads to graphs as the following one:
The text was updated successfully, but these errors were encountered: