The article explains how manually calculating absolute memory addresses for functions leads to error‑prone maintenance, introduces the concept of symbols to reference code by name, and details the role of object files, symbol tables, relocation tables, and the linking process that resolves addresses automatically.
Learn how Go’s embedded symbol table works, how to inspect and modify symbols using tools like nm and go tool nm, customize variables with ‑ldflags ‑X, and reduce binary size by stripping debug symbols, all illustrated with practical code examples.
The article explains how embedded developers can leverage cross‑compilation toolchains and the addr2line utility to quickly translate crash addresses into source file names and line numbers, dramatically improving debugging efficiency for native and kernel crashes.
This article provides an in‑depth technical overview of the ld64 static linker used in iOS builds, explaining its architecture, how it parses .o, .a and .dylib files, manages symbols, atoms and fixups, resolves undefined references, performs dead‑code stripping, and generates the final executable.
This comprehensive guide explains the inner workings of Apple's ld64 static linker for iOS, covering its historical background, core concepts such as objects, archives, symbols, and fixups, command‑line parameters, execution phases, symbol resolution, dead‑code stripping, optimization passes, output generation, auto‑linking, the -ObjC flag, debugging options, and LTO support.
The article explains Android native crashes (NE) by describing .so file composition, the need for un‑stripped libraries, how to view and generate stripped/un‑stripped binaries, and detailed workflows using ndk‑stack, DropBox, BreakPad, objdump, addr2line, and minidump_stackwalk to reconstruct stack traces and pinpoint source lines.
This article explains the detailed ELF file format—including ELF header, section and program header tables, various section types, and a practical Android native hook example—helping developers understand and troubleshoot native binary loading and symbol resolution.
