radareorg / radare2

UNIX-like reverse engineering framework and command-line toolset
https://www.radare.org/
GNU Lesser General Public License v3.0
20.6k stars 2.99k forks source link

oob 0xADDR #14300

Open s0i37 opened 5 years ago

s0i37 commented 5 years ago

Work environment

Questions Answers
OS/arch/bits (mandatory) Kali rolling x64
File format of the file you reverse (mandatory) PE/ELF
Architecture/bits of the file (mandatory) x86 32/64
r2 -v full output, not truncated (mandatory) radare2 3.6.0-git 22141 @ linux-x86-64 git.2.9.0-2532-gbb6f18b79

commit: bb6f18b79a4aa6a29950792b8fb8b06aaf40d09c build: 2019-06-07__10:55:43

Expected behavior

I expected full rebase to new base address (include functions list)

Actual behavior

The file content will rebase to new address. But analyze information is not.

Steps to reproduce the behavior

r2 a.out or a.exe aaa oob 0x10000000 afl

radare commented 5 years ago

Only the bininfo is rebased. The analysis, metadata, comments, xrefs , flags and so on is kept like it is. It is known issue and theres already an issue explaining whst to do to solve that but nobody did it yet. I am waiting to finish the rbin refactoring to continue in more base address refactorings that may lead fix this thing. The main complain of this is related to the debugger and aslr

On 14 Jun 2019, at 11:19, s0i37 notifications@github.com wrote:

Work environment

Questions Answers OS/arch/bits (mandatory) Kali rolling x64 File format of the file you reverse (mandatory) PE/ELF Architecture/bits of the file (mandatory) x86 32/64 r2 -v full output, not truncated (mandatory) radare2 3.6.0-git 22141 @ linux-x86-64 git.2.9.0-2532-gbb6f18b79 commit: bb6f18b build: 2019-06-07__10:55:43
Expected behavior

I expected full rebase to new base address (include functions list)

Actual behavior

The file content will rebase to new address. But analyze information is not.

Steps to reproduce the behavior

r2 a.out or a.exe aaa oob 0x10000000 afl

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.