From: Tom Lane <tgl@sss.pgh.pa.us>
To: Xu Haorong <db_haorong@outlook.com>
cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: Stack Smashing Detected When Executing initdb
In-reply-to: <959183.1719157695@sss.pgh.pa.us>
References: <TYZPR04MB81783A90E99EEE85978FF705F7CB2@TYZPR04MB8178.apcprd04.prod.outlook.com> <959183.1719157695@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Sun, 23 Jun 2024 11:48:15 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <983894.1719167529.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 23 Jun 2024 14:32:09 -0400
Message-ID: <983895.1719167529@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/983895.1719167529%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Xu Haorong <db_haorong@outlook.com> writes:
>> performing post-bootstrap initialization ... *** stack smashing detecte=
d ***: terminated
>> Aborted (core dumped)
>> child process exited with exit code 134

> No such problem is visible in our build farm [1], so what we have to
> figure out is how your machine is different from all of those.

Also, before you spend a lot of time chasing this, make sure it's
not a mirage.  Reset your source tree fully with "git clean -dfxq"
then configure, make, make install; then see if problem still exists.

If it does, the PG community's accumulated wisdom about getting stack
traces is here:

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_=
backend

Note that the "child process exited" message you show implies that the
failure was not in initdb itself, but in the single-user postgres
backend process that it spawns.  This means that any core file would
have been dumped into the created data directory, so you would have
to use initdb's --no-clean option to prevent it from being removed
immediately.

Also, if you are using a systemd-based Linux distribution, you may
have to negotiate with systemd-coredump to get back any core dump
at all.  "man 5 core" can be helpful reading here (personally
I just disable systemd-coredump per the directions shown there).

			regards, tom lane