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
Currently rdr makes bad distinctions between offsets and vmaddr. Unfortunately, our previous binary masters believed that embedding vmaddresses in the binary was the responsibility of the binary and not the loader and dynamic linker. This was foolish, but there's nothing we can do now.
So, because both have their uses, especially when debugging, a --vm switch might be a good idea to not perform automatic offset computations.
This will add complications, but might be necessary.
Alternatively, we could only return non-normalized binary offsets, and have a switch for returning binary offsets. Regardless, a consistent approach has to be taken, because right now it's a disassister, especially the --do switch.
The text was updated successfully, but these errors were encountered:
Currently
rdr
makes bad distinctions between offsets and vmaddr. Unfortunately, our previous binary masters believed that embedding vmaddresses in the binary was the responsibility of the binary and not the loader and dynamic linker. This was foolish, but there's nothing we can do now.So, because both have their uses, especially when debugging, a
--vm
switch might be a good idea to not perform automatic offset computations.This will add complications, but might be necessary.
Alternatively, we could only return non-normalized binary offsets, and have a switch for returning binary offsets. Regardless, a consistent approach has to be taken, because right now it's a disassister, especially the
--do
switch.The text was updated successfully, but these errors were encountered: