dd86k released this
on 23 May
Minor release featuring various work on object dumping.
The license was changed from BSD-3-Clause to BSD-3-Clause-Clear.
A new CLI module was introduced to keep options and behaviors consistent in both Alicedbg and Alicedump.
Long format options now require the equal sign (--example=
) with options that requires a value.
A new Alicedump configuration was created with its own set of options, to avoid polluting the debugger's set of options.
Alicedump is a direct alternative, but still work-in-progress, to tools such as objdump(1), nm(1), and readelf(1).
By default, without any specific data requested, a file(1)-like output is provided:
$ alicedump alicedump alicedump: Executable and Linkable Format (elf), Executable, for AMD x86-64 (amd64) machines $ alicedump alicedump.exe alicedump.exe: Portable Executable (pe32), Executable, for AMD x86-64 (amd64) machines
The --extract
option was added to allow for some binary information to be set to stdout, allowing data to be piped to other tools.
The --hexdump
option was added to allow for some binary information to be hexdumped and formatted on screen.
Support for OMF objects and libraries were initiated.
The Alicedbg library can now be compiled as a shared object (also known as a dynamically linked library).
The Linux static builds should work regardless of the host C runtime environment, such as glibc, because the executables do not rely on the host C runtime and includes its own.
--debug-info
to --build-info
.-a|--arch
to -m|--machine=
.disassemble
command uses EIP or RIP by default if no memory location was given.alicedump
command.--hexdump
. Certain elements can be dumped using Alicedump's internal hexdump printer.x86
machine was renamed to i386
for consistency.le
" as a short name if it is one (LX).