data_create_empty with size 0 calls malloc(0) — undefined behavior per C standard #74

New Issue

2026-07-20T17:14:37+02:00

TapTap commented

2026-07-20 17:14:37 +02:00

Description

In line 6, calls :

When is 0, has implementation-defined behavior. Per the C11 standard (7.22.3), may return NULL or a unique pointer. If it returns NULL, the caller treats this as an allocation failure, even though requesting 0 bytes is valid.

Several callers pass 0 to :

(line 38): — this calls but sets and , so it's fine.
(line 60): where is calculated — could be 0 if chunk has 0 files.

Location

Suggested Fix

Use as a safe minimum when is 0:

Severity

Low

Category

Bug

## Description In line 6, calls : When is 0, has implementation-defined behavior. Per the C11 standard (7.22.3), may return NULL or a unique pointer. If it returns NULL, the caller treats this as an allocation failure, even though requesting 0 bytes is valid. Several callers pass 0 to : - (line 38): — this calls but sets and , so it's fine. - (line 60): where is calculated — could be 0 if chunk has 0 files. ## Location ## Suggested Fix Use as a safe minimum when is 0: ## Severity Low ## Category Bug

TapTap referenced this issue from a commit

2026-07-20 18:44:11 +02:00

fix: memory/null safety bugs — issues #74, #72, #69, #64, #60, #50, #49, #65

TapTap closed this issue

2026-07-20 18:44:16 +02:00

TapTap referenced this issue

2026-07-20 18:44:16 +02:00

Fix memory/null safety bugs (#74, #72, #69, #64, #60, #50, #49, #65) #80

TapTap referenced this issue from a commit

2026-07-20 18:56:39 +02:00

fix: memory/null safety bugs — issues #74, #72, #69, #64, #60, #50, #49, #65

TapTap referenced this issue from a commit