fix bug in the parser of the hwids argument

when several delimiters follows one by one with no data between
one of them would be captured as part of the hwid or as a separate hwid
for example, ",hwid1,hwid2,," would be parsed as ",hwid1" "hwid2" ","
bug occurred due to missing update of hwid_begin

Author: XakerTwo

generate-cat-file.c

@@ -1189,7 +1189,7 @@ void parse_file_args(char **f_args, int f_count, char *os_attr, struct list_node
 	hwid_data->value = hwid_begin; \
 }
 
-//note: it does modify hwids content (replace comma with null) and creates references to its particular parts
+//note: it does modify hwids content (replace each comma, that comes 1st after hwid, with null) and creates references to its particular parts
 int parse_hwids_arg(char *hwids, struct list_node **hwid)
 {
 	struct list_node *hwid_last = NULL;
@@ -1199,13 +1199,17 @@ int parse_hwids_arg(char *hwids, struct list_node **hwid)
 
 	while (*hwids)
 	{
-		if (*hwids == ',' && hwids > hwid_begin)
+		if (*hwids == ',')
 		{
-			FUNC_CREATE_HWID_NODE();
-			
-			//"cut" string to current hwid end
-			*hwids = '\0';
-			//update current position and move position of current hwid begin to it
+			//check if delimiter is NOT immediately after another one (empty entries must be skipped, delimiter is not allowed in the value)
+			if (hwids > hwid_begin)
+			{
+				FUNC_CREATE_HWID_NODE();
+				
+				//"cut" string to current hwid end
+				*hwids = '\0';
+			}
+			//update current position AND move position of current hwid begin to it
 			hwid_begin = ++hwids;
 		}
 		else