glibc: Seven Easy Steps to Your First Patch
summary
Seven concrete steps guide getting a first glibc patch: build out-of-tree, write a failing test that simulates allocation failure with a fail-malloc test, implement a minimal fix (example: change strerror/strerror_l so they never return NULL by using asprintf and falling back to a static "Unknown error" string), add the test to the appropriate Makefile, run make check with glibc test helpers, and submit patch to libc-alpha.
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 1:34Understanding glibc
- 3:04Why contribute to glibc
- 5:54General contribution steps
- 8:05Anatomy of a glibc patch
- 13:12Implementing the fix
- 21:35Contribution opportunities
- 26:35Resources and Q&A
- 30:31Advanced contribution topics
related talks
27mBaby Steps to Kernel Hacking
45mFrom an Idea to a Patch in the Linux Mainline
34mContributing your first patch to the Qt Project
37mGetting Your Patches in Mainline Linux: What Not To Do (& a Few Things You Could Try
43mGetting to Know the Linux Kernel: A Beginner's Guide
49mMaking your patch more committable
46mGNU C Library
39mThe Life of a Kernel Bugfix