Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sLIvj-00EIp8-Sm for pgsql-general@arkaria.postgresql.org; Sun, 23 Jun 2024 08:50:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sLIvi-007bhF-5z for pgsql-general@arkaria.postgresql.org; Sun, 23 Jun 2024 08:50:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sLIvh-007bZk-M4 for pgsql-general@lists.postgresql.org; Sun, 23 Jun 2024 08:50:34 +0000 Received: from mail-vk1-xa31.google.com ([2607:f8b0:4864:20::a31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sLIvf-002hET-5Z for pgsql-general@postgresql.org; Sun, 23 Jun 2024 08:50:32 +0000 Received: by mail-vk1-xa31.google.com with SMTP id 71dfb90a1353d-4ef561f77eeso534863e0c.0 for ; Sun, 23 Jun 2024 01:50:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719132630; x=1719737430; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+GTOTT2MoAoo51U+JUUVp7kiwMDVGKLV5uSRPHFIyag=; b=gUkCPuauKHkasg/jxnPNMhSdrxcaZc5oBrYO5LjcFC9ZbV09l/zIf3QeTtRzuSb/fk NBk+U3giwOHcVnOa1XBWMs28C4dLrA5oGgrW98IdjxIgrYzeggaUBPLw8XWofo/JwtA7 v2XOewhZ+vH7xe4DS/KxYKEICcbtvl/3bIzQdQhGR3+GUZ/D8LLyP9Ew+jaiwAp1x5Kb ohutaSQFx15dudpKu1fxsk9lULepTuLyLDWQ790wzfVo8pZjGNN53wVgEus+DYMnImV3 m3tJ5w1j3Uw5oEfGbCMbTHyVSJb9sMax0wnALUR4ayG0Du47o64npPObjieiq6DDjTeY aINg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719132630; x=1719737430; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+GTOTT2MoAoo51U+JUUVp7kiwMDVGKLV5uSRPHFIyag=; b=A27D5m7uC1b/CLFmHlGBjlJtDtXfGOryCGhUMxMBqLU/fRGNyGaVyK0toHHwd8FgEk upZCHYLPeEBVji/RjHnR2K6SI/pTPbaOCiK1GBp+oe4mFfKnCaOLDnEbgK1QmxQX/rCM l5ADdJ2EGOib0lisc6betS4B8DstUk0jTWKfTyJgwTXSkgDqR3gMxfczh9y6AXwV3jjp s8fQzupOLeJxpdwWI/GPF91/RJpgKg5gObJPvzulRkXLUvMdvOwLcmMMW7/5LX10BY1l H2QZbbIsj95RodLWb4rP00gXzSZP4owbXnNymCCQoXGx/29sdS1fV7TP1sgIuiGhi17q v1EQ== X-Gm-Message-State: AOJu0Ywms3HZI+/phCG/zk/Klv+MJM6BI9WrmFtW8Xaab94qdJ9n5WvL alFie+Biy9pOZ8CKEJbSwMxeW5goOzFJ9JVGsIGgyzVJrGWC2AbpFcG/5umRdxxMHfRJp+78rzS vA7fJshi2InumOSYplfrs6VRt3Q0= X-Google-Smtp-Source: AGHT+IHlOIGA90Nqz+oKJy3P3n+bQudv4dGxGGqvNiVJylYYqgMUL6weOXVQqRsfAMWXDwFxYVlOP2KrxdJLviFJaJg= X-Received: by 2002:a67:bd0f:0:b0:48f:3930:4a82 with SMTP id ada2fe7eead31-48f4f09f918mr1106605137.23.1719132630094; Sun, 23 Jun 2024 01:50:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kashif Zeeshan Date: Sun, 23 Jun 2024 13:50:18 +0500 Message-ID: Subject: Re: Stack Smashing Detected When Executing initdb To: Xu Haorong Cc: "pgsql-general@postgresql.org" Content-Type: multipart/alternative; boundary="000000000000bd1bb3061b8ac15a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bd1bb3061b8ac15a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Xu To pinpoint the issue, please use gdb debugger to get the backtrace to exactly find out where the error is occurring and you can then do the required setups. For Reference : https://stackoverflow.com/questions/50093327/how-do-i-solve-postgresql-abor= ted-core-dumped-error Thanks Kashif Zeeshan On Sun, Jun 23, 2024 at 12:19=E2=80=AFPM Xu Haorong wrote: > Hi everyone, > > Today I tried to build the latest devel version of PostgreSQL(commit > 70a845c04a47645b58f8276a6b3ab201ea8ec426). The compilation was successful= , > but when I ran initdb an error occured: > > /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data > The files belonging to this database system will be owned by user > "postgres". > This user must also own the server process. > > The database cluster will be initialized with locale "en_US.UTF-8". > The default database encoding has accordingly been set to "UTF8". > The default text search configuration will be set to "english". > > Data page checksums are disabled. > > fixing permissions on existing directory /usr/local/pgsql/data ... ok > creating subdirectories ... ok > selecting dynamic shared memory implementation ... posix > selecting default "max_connections" ... 100 > selecting default "shared_buffers" ... 128MB > selecting default time zone ... Asia/Shanghai > creating configuration files ... ok > running bootstrap script ... ok > *performing post-bootstrap initialization ... *** **stack smashing > detected** ***: terminated* > *Aborted (core dumped)* > *child process exited with exit code 134* > *initdb: removing contents of data directory "/usr/local/pgsql/data"* > > After searching for solutions on the Internet, I disabled the stack > smashing protector by performing > *./configure CC=3D'clang -fno-stack-protector'* > > However, the problem still exists. Is there anyone else having this issue= ? > > Regards, > Haorong Xu > --000000000000bd1bb3061b8ac15a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Xu

To pinpoint=C2=A0the issue, pleas= e use gdb debugger=C2=A0to get the backtrace to exactly find out=C2=A0where= the error is occurring and you can then do the required setups.
=



Thanks
Kashif Zeeshan

=
On Sun, Jun 23, 2024 at 12:19=E2=80= =AFPM Xu Haorong <db_haorong@o= utlook.com> wrote:
Hi everyone,=C2=A0

Today I tried to build the latest devel version of PostgreSQL(commit 70a845= c04a47645b58f8276a6b3ab201ea8ec426). The compilation was successful, but wh= en I ran initdb an error occured:

/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user "pos= tgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8"= ;.
The default database encoding has accordingly been set to "UTF8".=
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /usr/local/pgsql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default "max_connections" ... 100
selecting default "shared_buffers" ... 128MB
selecting default time zone ... Asia/Shanghai
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... *** stack smashin= g detected=C2=A0***: terminated
Aborted (core dumped)
child process exited with exit code 134
initdb: removing contents of data directory "/usr/local/pgsql/data&= quot;

After searching for solutions on the Internet, I disabled the=C2=A0stack sm= ashing protector by performing
./configure CC=3D'clang -fno-stack-protector'

However, the problem still exists. Is there anyone else having this issue?<= /div>

Regards,
Haorong Xu
--000000000000bd1bb3061b8ac15a--