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
In this context, the OSACA parser seems not to be aware of the hex-notation
and that 0x64 is equal to 100, etc.
Looking at match_bytes there's a just a string comparison
if extracted_bytes[0 : len(byte_list)] == byte_list:
(cmp. marker_utils, line 191)
and unfortunately (['0x64', '0x67', '0x90'] != ['100', '103', '144'])
the markers are not found.
They have to be manually converted from hexadecimal to decimal
or (alternatively) the -l Option to manually set the lines range has to be used.
A quick hack could be just to replace the match_bytes line 191 (see above) with
if all([int(e1,0) == int(e2,0) for e1, e2 in zip(extracted_bytes[0 : len(byte_list)], byte_list)]):
Maybe converting and storing (& comparing) bytes as integers instead of strings might be another option.
The text was updated successfully, but these errors were encountered:
Looking at iacaMarks.h for IACA version 2.1, 2.2, 2.3 and 3.0,
there's
which leads (e.g. using
gcc -S
) toand
which corresponds to the
find_marked_kernel_x86ATT
(cmp. marker_utils, line 58)
In this context, the OSACA parser seems not to be aware of the hex-notation
and that 0x64 is equal to 100, etc.
Looking at
match_bytes
there's a just a string comparison(cmp. marker_utils, line 191)
and unfortunately (['0x64', '0x67', '0x90'] != ['100', '103', '144'])
the markers are not found.
They have to be manually converted from hexadecimal to decimal
or (alternatively) the -l Option to manually set the lines range has to be used.
A quick hack could be just to replace the match_bytes line 191 (see above) with
Maybe converting and storing (& comparing) bytes as integers instead of strings might be another option.
The text was updated successfully, but these errors were encountered: