Constant Memory leak found at this trace

Constant Memory leak found at this trace.
Every time we try to search in CLI,

==7781== LEAK SUMMARY:

==7781== definitely lost: 114 bytes in 20 blocks
==7781== 114 bytes in 20 blocks are definitely lost in loss record 85 of 90

Trace

==7781== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7781== by 0x4E3971F: cli_parse_line.constprop.5 (libcli.c:670)
==7781== by 0x4E3CD13: cli_loop (libcli.c:989)
==7781== by 0x4010A1: main (in /home/kalyan/cloutra/src/cli/a.out)

Function to be fixed

cli_parse_inline

Snap

while (nwords < max_words - 1)
{
    if (!*p || *p == inquote || (word_start && !inquote && (isspace(*p) || *p == '|')))
    {
        if (word_start)
        {
            int len = p - word_start;

            memcpy(words[nwords] = malloc(len + 1), word_start, len); <== later, this is not freed properly
            words[nwords++][len] = 0;
        }

Navigation Menu

Repository navigation

Constant Memory leak found at this trace #22

==7781== LEAK SUMMARY:

Trace

Function to be fixed

Snap

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Constant Memory leak found at this trace #22

Description

==7781== LEAK SUMMARY:

Trace

Activity

kaprakashr commented on Jan 19, 2016

Function to be fixed

Snap

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions