Detect Use-After-Free with Pointer Analysis in a C++ Codebase
Overview
What this challenge is about.
Write a Clang checker for a game engine to detect use-after-free with pointer analysis, then validate results. Earn a verifiable certificate.
The scenario
The vendor (used in roughly 4K shipped indie games, primary fix priority is crash rate) cannot wait for use-after-free crashes to surface in production — they need static evidence the team can act on.
The Brief
What you'll do, and what you'll demonstrate.
Find use-after-free bugs in a 220K-line C++ codebase using pointer analysis and deliver a triaged candidate list with above 50 percent confirmed-bug rate in the top 30.
Earning criteria — what you'll demonstrate
- Implement an Andersen-style pointer analysis in a real checker
- Reason about may-alias vs must-alias in pointer-analysis design
- Write a custom Clang static-analyzer checker end-to-end
- Triage static-analysis output honestly with confirmed/FP buckets
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Pointer Analysis
Apply pointer analysis to solve real industry problems and demonstrate production-level capability.
- Static Analysis
Apply static analysis to solve real industry problems and demonstrate production-level capability.
- Use After Free
Apply use after free to solve real industry problems and demonstrate production-level capability.
- C Plus Plus
Apply c plus plus to solve real industry problems and demonstrate production-level capability.
- Clang
Apply clang to solve real industry problems and demonstrate production-level capability.
- Ast
Apply ast to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles: