Unsafe code #49

Closed
opened 2025-11-10 06:49:23 +00:00 by jabber.developer · 1 comment

Some code parts are unsafe: lacking null-checks, potential double-frees etc. These parts need to be addressed.

Some code parts are unsafe: lacking null-checks, potential double-frees etc. These parts need to be addressed.
jabber.developer added this to the Plans (2025-2026) project 2025-11-10 12:25:47 +00:00
jabber.developer moved this to In Progress in Plans (2025-2026) on 2025-11-10 12:37:08 +00:00
jabber.developer2 self-assigned this 2025-11-10 13:12:41 +00:00
jabber.developer2 added reference playground/fix/src_refactoring 2025-11-10 13:12:51 +00:00
jabber.developer moved this to Verification in Plans (2025-2026) on 2026-01-16 15:41:03 +00:00
jabber.developer moved this to In Progress in Plans (2025-2026) on 2026-01-16 15:41:24 +00:00
jabber.developer added the
Kind/Security
Priority
High
2
Reviewed
Confirmed
1
labels 2026-01-21 16:41:22 +00:00
Author
Owner

Mostly resolved by #47. Current issue lack specific details. If unsafe parts are reencountered/could be automatically detected, they are going to be referenced in new issues.

Mostly resolved by #47. Current issue lack specific details. If unsafe parts are reencountered/could be automatically detected, they are going to be referenced in new issues.
jabber.developer moved this to Done in Plans (2025-2026) on 2026-02-11 08:43:49 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: devs/cproof#49
No description provided.