C Code Review for Benign Issues | Dataford Interview Questions

What do you look for when reviewing C code for errors that might seem benign in a small project but are risky in production?

Implement a lightweight analyzer for a C source string. Return each applicable risk category at most once, ordered by the first occurrence of that category in the source. Ignore code inside // and /* ... */ comments. Treat an allocation as checked when its assigned variable is later compared with NULL or 0.

Input: one C source string. Output: a list of risk labels.

Constraints

0 <= len(code) <= 5000
code contains a single C source string
Return each risk label at most once
Recognized labels are unsafe_input, unsafe_string_operation, format_string, and unchecked_allocation

Function Signature

def analyze_c_risks(code):

Your question is C Code Review for Benign Issues. Start with the requirements in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

Problem

What do you look for when reviewing C code for errors that might seem benign in a small project but are risky in production?

Input: one C source string. Output: a list of risk labels.

Constraints

0 <= len(code) <= 5000
code contains a single C source string
Return each risk label at most once
Recognized labels are unsafe_input, unsafe_string_operation, format_string, and unchecked_allocation

Function Signature

def analyze_c_risks(code):

Your question is C Code Review for Benign Issues. Start with the requirements in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.