Add support to raise relocatable binaries (.o) about llvm-mctoll HOT 7 CLOSED

I think it is certainly possible to modify the tool to read raw binary along with any additional information - such as function boundaries specified in a pre-defined format.

You can consider adding

1. a couple of inter-dependent new command-line options - say --raw-binary <binary-filename> and --function-map <funcmap-filename>
2. an implementation - say DisassembleRawBits(char * BinaryFilename, char *FuncMapFilename) - that consumes the raw binary and function map file provided to create the MCInstRaiser::mcInstMap using MCInstRaiser::addMCInstOrData(uint64_t index, MCInstOrData mcInst). This can be called instead of DisassembleObject(File *, bool) in llvm-mctoll.cpp.

Once the instruction map of a function is constructed, the rest of the tool's existing infrastructure can be leveraged unchanged.

Hope that helps.

from llvm-mctoll.

Raising object files is not supported. The tool is designed with an intent to raise only executables (which includes shared libraries).

from llvm-mctoll.

Instead of crashing, a possible improvement is for mctoll to check that the elf binary is executable and if not issue an appropriate message and exit. We probably also want a command line option to override this and force the raising.

from llvm-mctoll.

if (Elf.getEType() != ELF::ET_EXEC && Elf.getEType() != ELF::ET_DYN)
report_fatal_error("Only ELF executables and shared libraries are supported. Use -f to force raising anyway.");

from llvm-mctoll.

Commit 8e5e96c adds code to gracefully exit an attempt raise relocatable ELF binaries (.o files).

The use case / need to raise .o files has to be clearly identified. If there is indeed a justifiable use case, support to raise .o files should be added. Once that support is added, there should be no need for user to force it using an additional flag.

from llvm-mctoll.

hi. i am trying to integrate llvm-mctoll as a plugin into ghidra
is there by any chance a way to mod it to accept some raw binary (ie: not an elf file) a ram dump of arm micro-controller.
i have the complete disassembly control flow instruction function boundary ie: where are function offsets and data offsets are. even data struct...

from llvm-mctoll.

I patched llvm-objcopy to support elf32-bigarm. Kinda strange objcopy don't handle it while backend do emit bigendian at least for powerpc...

Then used it to build an elf file with .text & .data .
set their flags and address hopefully ok.

However still trouble the McCool complains

This arch has not yet supported raising

I am wondering if the tool raiser has support for arm 32bit mode and 16bit thumb mode. Or it only support Aarch64...

I used a qemu emulator front-end to auto unpack the rom image to the ram and dump it.

from llvm-mctoll.