search

angr / angr-targets

This repository contains the currently implemented angr concrete targets.
32 stars 9 forks source link

AvatarGDBConcreteTarget for arm #23

Closed SteinsGatep001 closed 2 years ago

SteinsGatep001 commented 2 years ago

Trying to create a gdb concrete target using AvatarGDBConcreteTarget(avatar2.archs.arm.ARM, 'localhost', port).

avatar_gdb = AvatarGDBConcreteTarget(avatar2.archs.arm.ARM, 'localhost', port)
p = angr.Project(target, concrete_target=avatar_gdb, use_sim_procedures=True)

But it shows that:

angr.project.CRITICAL | Concrete execution does not support yet the selected architecture. Aborting.

Should I add the concrete for this architecture myself or is there already another branch that supports this arch?

degrigis commented 2 years ago

@SteinsGatep001 sorry for the late response, this sled under my radar. It seems that there is a mismatch between the string ID used by Avatar2 for ARM and the one we are expecting when creating a concrete target? See here https://github.com/angr/angr/blob/master/angr/project.py#L170 Can you see what's the ID of the reported ARCH when you declare the avatar_gdb object?

SteinsGatep001 commented 2 years ago

the binary archis : Arch ARMEL (LE)

SteinsGatep001 commented 2 years ago

I add "ARMEL" to ['X86', 'AMD64', 'ARMHF', 'MIPS32']: https://github.com/angr/angr/blob/master/angr/project.py#L170 , it works but it is a trick. Any other methods?

degrigis commented 2 years ago

Providing that you know how to synchronize the concrete state of a program running on ARMEL (the best case scenario is that under the hood is the same as ARMHF), you should be good with that simple modification.