Fix a Shared C Code Snippet | Dataford Interview Questions

Given a C code snippet in a shared Google Doc, explain what is wrong with it.

Asked in the Technical interview 1 stage. Casual first technical round.

Implement explain_c_issues(code), which returns recognized issue labels in this order when present: unsafe_input, unchecked_allocation, unsafe_copy, string_pointer_comparison, and missing_free. Return each label at most once. The input is a C source snippet as a string, and the output is a list of strings. Detect gets, unchecked malloc, strcpy, comparisons between declared character strings or character pointers, and allocated memory that is never freed.

Constraints

code is a string containing at most 5,000 characters.
Issue labels must be returned in the specified order.
Each issue label appears at most once.
The analysis is lexical and does not need to compile the C source.

Function Signature

def explain_c_issues(code):

Your question is Fix a Shared C Code Snippet. 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

Given a C code snippet in a shared Google Doc, explain what is wrong with it.

Asked in the Technical interview 1 stage. Casual first technical round.

Constraints

code is a string containing at most 5,000 characters.
Issue labels must be returned in the specified order.
Each issue label appears at most once.
The analysis is lexical and does not need to compile the C source.

Function Signature

def explain_c_issues(code):

Your question is Fix a Shared C Code Snippet. 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.