-
Notifications
You must be signed in to change notification settings - Fork 13
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
Use explicit data types with pandas #42
Comments
Just out of interest: is it negative because the memory address is a unsigned address value interpreted as a signed? |
No, the addresses are always interpreted correctly. I am not sure what the underlying problem is. Could be because there are mixed data types (signed and unsigned integers in this case) in the pandas data structure. |
lukasauer
added a commit
to lukasauer/archie
that referenced
this issue
Aug 2, 2022
The call to pandas.concat in write_output_wrt_goldenrun() causes large integer registers values to be cast to floats. Since the register values do not have to be deduplicated, do not process them with write_output_wrt_goldenrun(). See also Fraunhofer-AISEC#41 and Fraunhofer-AISEC#42
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pandas may sometimes choose to convert large integers (close to 64-bit integer limit) to floats. This is very common on register dataset on 64-bit architecture and is fixed with #41. Similar situation in the code base should be fixed as well. This problem is likely to also occur if a target binary is mapped to a negative memory address (typical for kernels).
The text was updated successfully, but these errors were encountered: