#737 Memory leak in INI
Closed: Invalid None Opened 13 years ago by dpal.

Function

     static char **get_str_cfg_array(struct collection_item *item,
   46                                int include,
   47                                const char *sep,
   48                                int *size,
   49                                int *error)

will leak memory if the config string starts from spaces.
It looks like the optimization that I tried to implement has a flaw. I do not see a way to overcome this issue other than rewrite the function to copy data for each string in the array.


Fields changed

coverity: => 10043
keywords: => Coverity

Fields changed

coverity: => 10043
keywords: => Coverity

Fields changed

coverity: => 10043
keywords: => Coverity

I took a closer look at this one. I think I misread the code. I added a unit test for the case that I suspected might fail but it passed and I think after reading code again that it is correct.
Closing the issue.

resolution: => invalid
status: new => closed

I took a closer look at this one. I think I misread the code. I added a unit test for the case that I suspected might fail but it passed and I think after reading code again that it is correct.
Closing the issue.

resolution: => invalid
status: new => closed

I took a closer look at this one. I think I misread the code. I added a unit test for the case that I suspected might fail but it passed and I think after reading code again that it is correct.
Closing the issue.

resolution: => invalid
status: new => closed

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Metadata Update from @dpal:
- Issue set to the milestone: Tools Backlog

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1779

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata