When bad C code puts you behind bars... @Fireship
When bad C code puts you behind bars...  @Fireship
Uploaded June 2025 | Updated September 2026, 2 weeks ago
Start building with Gel today: bit.ly/4mTm2D7

These 5 simple examples of memory management in C have the potential to cost your company billions of dollars or even put you in jail.

#C #coding #programming

πŸ’¬ Chat with Me on Discord

discord.gg/fireship

πŸ”— Resources
- iso.org/standard/82075.html

πŸ“š Chapters
- Bad bounds checking
- Heartbleed bounds check
- Using memory after it's been free()ed
- Off-By-One
- Double free()

πŸ”₯ Get More Content - Upgrade to PRO

Upgrade at fireship.io/pro
Use code YT25 for 25% off PRO access

🎨 My Editor Settings

- Atom One Dark
- vscode-icons
- Fira Code Font

πŸ”– Topics Covered

- Memory management in C
- malloc() and free() in C
- Bounds checking in C
- The Morris Worm
- What caused Heartbleed?
When bad C code puts you behind bars...The Internets most broken protocolHow AI is breaking the SaaS business model...Claude Mythos is too dangerous for public consumption...GitHub is having some major issues right now…Paying for software is stupid… 10 free and open-source SaaS replacementsRaspberry Pi Explained in 100 Seconds10 regrets of experienced programmerslol Apple Intelligence is dumb...One man just liberated Fable... and now it’s illegal5 life-changing Linux tipsAWS just released its Cursor killer…
Fireship |

When bad C code puts you behind bars...

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER