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
- 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.
- 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.
- Validate name choices by cross-referencing the partial git history.
- 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
- String cross-references in Ghidra usually let you label 30-40 percent of functions on the first pass
- objdump -d is faster for one-off lookups; Ghidra is necessary once you're cross-referencing
- 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.
Finish it. Earn this.
A verified certificate with your name. Anyone can check it.
Time to practice.
Solve this challengeMore like this.
- Software EngineerBuild a Multi-Level Feedback Queue Scheduler in xv6
- Software EngineerImplement a Distance-Vector Routing Algorithm
- AI EngineerEnd-to-End Lane Following on a Donkeycar Platform
- NLP EngineerLLM-Powered FAQ Chatbot for 40-Person SaaS Scale-up
-
Build a Multi-Level Feedback Queue Scheduler in xv6 Software Engineer Fork the xv6-riscv repository and implement MLFQ in proc.c with 3 priority queues, per-queue time slices (10ms / 20ms / 40ms), priority demotion on sl operating systemsschedulingc programming Open challenge → -
Implement a Distance-Vector Routing Algorithm Software Engineer Implement distance-vector routing in Python: each simulated router maintains a distance vector, exchanges vectors with neighbors every 1 second of sim routingdistance vectornetwork simulation Open challenge → -
End-to-End Lane Following on a Donkeycar Platform AI Engineer Use the public Donkeycar Tub dataset (or collect about 30 minutes of driving on the simulator). Train a CNN-policy baseline (the Donkeycar default arc end to end learningimitation learningpytorch Open challenge → -
LLM-Powered FAQ Chatbot for 40-Person SaaS Scale-up NLP Engineer You have access to TaskFlow's internal documentation, help articles, and a sample of 500 support tickets. Your task is to build a retrieval-augmented llmraginformation retrieval Open challenge →