Open alvarofe opened 5 years ago
I don’t think it’s a regression. We can easily test on 2 releases ago anyway... however it happened to me too and I have some doubts about the whole base/laddr concept.
For your particular case, why don’t you use -B?
I can confirm it was happening in radare2-2.9.0 too.
-B it is what I use, I was trying to understand why there were tests failing in my PR and I noticed this behaviour.
-B is what you should use if the bin have headers. Use only -m when messing with raw dumps
On 14 Nov 2018, at 09:19, Álvaro Felipe Melchor notifications@github.com wrote:
-B it is what I use, I was trying to understand why there were tests failing in my PR and I noticed this behaviour.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
This issue has been automatically marked as stale because it has not had recent activity. Considering a lot has changed since its creation, we kindly ask you to check again if the issue you reported is still relevant in the current version of radare2. If it is, update this issue with a comment, otherwise it will be automatically closed if no further activity occurs. Thank you for your contributions.
While working on arm analysis I noticed that files which are loadded by mapping it into another direction with
-m
was not setting the bits hints correctly.However, if loaded normally
This is gonna affect the analysis enormously on arm due to missing anal hints. Furthermore, there are some
WARNINGS
andTODO
.The issue is here in
r_bin_open_io
seekaddr
will be what is was passed to-m
and this should be 0 since the file is paddr so later oncheck_bytes
can detect correctly the bin plugin.I believe @ret2libc is working on refactoring this - dunno if a regression.
Due to this issue my PR https://github.com/radare/radare2/pull/12068 will have some [XX].
Example
The functions should be the same independently where the binary was loaded.