Changes between Version 1 and Version 2 of Ticket #22417, comment 11


Ignore:
Timestamp:
May 28, 2017, 12:34:07 AM (21 months ago)
Author:
Jigsaw52
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #22417, comment 11

    v1 v2  
    33The bug was triggered by including a folder with a non-empty file without any values followed by another file.
    44
    5 The problem is in the config_process_include() function. When this function is called to process an included folder, it will call config_get_included_list() for each file in the folder. config_get_included_list() will write the list of values on the file to included_list and the pointer to the last entry of the list to list_last. When a file contains no values, both included_list and list_last will be null. The bug is that, after calling config_get_included_list(), we update the the *next pointer with the following code:
     5The problem is in the config_process_include() function. When this function is called to process an included folder, it will call config_get_included_list() for each file in the folder. config_get_included_list() will write the list of values on the file to included_list and the pointer to the last entry of the list to *list_last. When a file contains no values, both included_list and *list_last will be null. The bug is that, after calling config_get_included_list(), we update the the *next pointer with the following code:
    66
    77{{{