Re: Report a potential memory leak in setup_config()

From: wliang(at)stu(dot)xidian(dot)edu(dot)cn
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andres Freund" <andres(at)anarazel(dot)de>, "Daniel Gustafsson" <daniel(at)yesql(dot)se>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Report a potential memory leak in setup_config()
Date: 2022-02-16 08:13:26
Message-ID: 7c309428.1c60.17f0197e491.Coremail.wliang@stu.xidian.edu.cn
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

By the way,

This html files are the bug reports produced by static detection of clang's MallocChecker.

All of those bugs are the memory leak bugs in the initdb.c.

Some of them shares the same reason to the one I reported yesterday, while some of them are not.

Since you guys have already got the patch and fixed the problem, I don't know if it is too late to send this email.

However, if you can confirm those bugs really exist, it will be a great help to my study.

Once again, I want to give you my sincerely thanks.

regards,

Wentao

Attachment Content-Type Size
report-0c40f6.html text/html 603.3 KB
report-4ded84.html text/html 602.6 KB
report-55f328.html text/html 602.6 KB
report-a28ac0.html text/html 610.2 KB
report-da7c7f.html text/html 603.2 KB
report-e80982.html text/html 603.1 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Victor Yegorov 2022-02-16 08:14:49 Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
Previous Message wliang 2022-02-16 07:13:27 Re: Report a potential memory leak in setup_config()