More summaries and tags
This commit is contained in:
@@ -2,7 +2,17 @@
|
||||
author: "Halvo (Human)"
|
||||
title: "Set to NULL After Free: Summations of Secure Coding in C and C++"
|
||||
date: 2022-08-17
|
||||
tags:
|
||||
- free-and-null
|
||||
- secure-coding
|
||||
- c
|
||||
- cpp
|
||||
- memory-management
|
||||
- pointers
|
||||
- security
|
||||
draft: false
|
||||
summary: |
|
||||
A breezy, slightly tongue‑in‑cheek look at why setting pointers to `NULL` right after `free` (and a few related memory‑management niceties) can save you from nasty use‑after‑free bugs, memory leaks, and the occasional midnight debugging panic.
|
||||
---
|
||||
|
||||
## Introduction
|
||||
|
||||
Reference in New Issue
Block a user