Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nKMNZ-0007WU-BR
	for pgsql-bugs@arkaria.postgresql.org; Wed, 16 Feb 2022 15:38:05 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nKMNX-0001Xv-4l
	for pgsql-bugs@arkaria.postgresql.org; Wed, 16 Feb 2022 15:38:03 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nKMNW-0001Xl-T7
	for pgsql-bugs@lists.postgresql.org; Wed, 16 Feb 2022 15:38:02 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nKMNT-0000PA-HB
	for pgsql-bugs@lists.postgresql.org; Wed, 16 Feb 2022 15:38:02 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 21GFboSF3311469;
	Wed, 16 Feb 2022 10:37:52 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: wliang@stu.xidian.edu.cn
cc: "Andres Freund" <andres@anarazel.de>,
        "Daniel Gustafsson" <daniel@yesql.se>,
        pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: Report a potential memory leak in setup_config()
In-reply-to: <383f52a7.1780.17f0160fa32.Coremail.wliang@stu.xidian.edu.cn>
References: <64ee7543.20d.17efb1270ca.Coremail.wliang@stu.xidian.edu.cn>
 <A7070803-5A15-486E-AE04-ECC13CD10038@yesql.se>
 <3052163.1644942806@sss.pgh.pa.us>
 <20220216012953.6d7bzmsblqou3ru4@alap3.anarazel.de>
 <3239746.1644975946@sss.pgh.pa.us>
 <20220216022118.vvijtgd5rl2b6ucv@alap3.anarazel.de>
 <3243399.1644978358@sss.pgh.pa.us> <3244453.1644979091@sss.pgh.pa.us>
 <20220216041049.uy3vwtk6ry66g6um@alap3.anarazel.de>
 <3255493.1644985807@sss.pgh.pa.us>
 <383f52a7.1780.17f0160fa32.Coremail.wliang@stu.xidian.edu.cn>
Comments: In-reply-to wliang@stu.xidian.edu.cn
	message dated "Wed, 16 Feb 2022 15:13:27 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3311467.1645025870.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Feb 2022 10:37:50 -0500
Message-ID: <3311468.1645025870@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/3311468.1645025870%40sss.pgh.pa.us>
Precedence: bulk

wliang@stu.xidian.edu.cn writes:
> I would like to know the name of the software which is used to calculate=
 the size of leaked memory.

I was using valgrind, and I think Andres was too:

https://valgrind.org

			regards, tom lane