Fatal bug when trying to validate protocols in device-sdk-c

[GabrielMonS]

🐞 Bug Report

Affected Services [REQUIRED]

The issue is located in: device-sdk-c

Is this a regression?

Yes, the previous version in which this bug was not present was: N/A

Description and Minimal Reproduction [REQUIRED]

When setting a address validate function (using the devsdk_callbacks_set_validate_addr() function of the sdk), the service calls the function convert_protocols() located in validate.c(line 14). This function is unable to retrieve the protocol name or properties and throws a segmentation fault when trying to assign a 'null' to the devsdk_protocols object's fields (protocol->name and protocol->properties). This segfault in turn kills the whole service.

In order to reproduce it, you can use a template for device service, add a validate_address function, compile the template and run it, and try to add a device to the service. It will crash.

🔥 Exception or Error

Last prints I get (including custom ones I have put, the ones that start with [PROTOCOLS_CONVERT]:

level=INFO ts=2025-02-03T13:59:02Z app=device-random msg="Processing Devices from ./res/devices"
[PROTOCOLS_CONVERT]: Entering protocol convert function
[PROTOCOLS_CONVERT]: Entering protocol search loop
[PROTOCOLS_CONVERT]: Protocol 0, Name: (null)
Segmentation fault

🌍 Your Environment

Deployment Environment: Ubuntu 22.04 on AMD64 system.

EdgeX Version [REQUIRED]: EdgeX version: 3.1.1 / device-sdk-c version: 4.0.0-dev1

Anything else relevant?