What problem does it solve? Reverse engineers constantly hit the problem of addresses not matching: the address shown in Ghidra differs from the runtime address in gdb, which differs again from what angr or frida reports. This Skill provides a unified procedure for translating between file offsets, link-time addresses, and runtime addresses so breakpoints, symbol lookups, and cross-tool comparisons actually line up. ## Core Features & Use Cases - Static base and RVA/VA conversion: Determine the link-time base from ELF program headers (readelf) and convert between file offsets, RVAs, and virtual addresses per segment. - Runtime base resolution under PIE/ASLR: Compute the load bias dynamically from /proc/pid/maps, gdb info proc mappings, or frida module base APIs, handling separate-code layout differences. - Cross-tool address alignment: Reconcile addresses between Ghidra, angr (mapped_base/rebase), gdb, and frida by anchoring everything to the runtime base. - Firmware loader offset: Reverse-engineer the delta between a firmware image's link address and its actual load address from boot code. - Use Case: You set a breakpoint in gdb at the address Ghidra shows for a function in a PIE binary and it never hits. Use this Skill to compute the load bias from the process maps and relocate the breakpoint correctly. ## Quick Start Ask the AI to compute the runtime address of a function at link-time offset 0x1234 in a PIE binary given its process ID, using the address-space conversion procedure.