Ewance
← All challenges Software Engineer

Reverse-Engineer a Stripped Binary to Restore Linking Symbols

Duration
2 weeks
Level
Intermediate
Type
Code
Team
1 to 5 people

The situation

The studio (planning a console port that requires a clean crash-reporting pipeline) cannot release without symbol-level crash data for the anti-cheat library.

Your task

Restore at least 30 reasonable function symbols to a stripped 6-year-old library and produce a symbol file the modern build pipeline can consume.

The brief

What you do

  1. Receive the stripped shared object (Linux ELF, x86-64, ~280KB), a crash dump with 12 frames of indecipherable addresses, and 4 years of partial git history with some related (but not identical) source.
  2. Use objdump + nm + Ghidra to walk the binary, identify functions by call-graph + string-reference patterns, and label at least 30 functions with reasonable names.
  3. Validate name choices by cross-referencing the partial git history.
  4. Produce a .symtab patch (or a separate .debug file) the modern build pipeline can load via DWARF or addr2line.

You deliver

The Ghidra project, the restored symbol file, the crash-dump re-symbolized, and a 3-page methodology note for the QA + build team.

What you will practice

  • Use objdump, nm, and Ghidra to navigate a stripped ELF binary
  • Identify functions by call-graph patterns and string references
  • Restore symbols compatible with the addr2line / DWARF toolchain
  • Document a reverse-engineering methodology others can extend

A suggested way in

  1. String cross-references in Ghidra usually let you label 30-40 percent of functions on the first pass
  2. objdump -d is faster for one-off lookups; Ghidra is necessary once you're cross-referencing
  3. GNU binutils objcopy --add-gnu-debuglink is the cleanest way to attach a separate debug file

Skills you will practice

Reverse engineering, Linking and loading, Machine code, Ghidra, Elf, Documentation

How it is assessed

  • Symbol coverage30%

    At least 30 functions labeled with defensible names.

  • Naming quality25%

    Names reflect actual behavior, cross-validated where possible.

  • Build integration25%

    Symbol file is consumable by the modern build pipeline.

  • Methodology note20%

    QA + build team can repeat the process on the next stripped library.

Resources

  • GhidraTool

    Primary reverse-engineering platform.

  • objdumpTool

    Quick disassembly of specific functions.

  • nmTool

    Symbol-table inspection.

  • addr2lineTool

    Validate that crash addresses resolve to the restored symbols.

  • GitTool

    Cross-reference partial source history.

  • NotionTool

    Author methodology note.

Sample Ewance certificate of completion, verified by LearnCoin
Sample certificate
Your proof

Finish it. Earn this.

A verified certificate with your name. Anyone can check it.

Time to practice.

Solve this challenge
Related challenges

More like this.