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-aborted-core-dumped-error
Thanks
Kashif Zeeshan
On Sun, Jun 23, 2024 at 12:19 PM Xu Haorong <db_haorong@xxxxxxxxxxx> 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/dataThe 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 ... okcreating subdirectories ... okselecting dynamic shared memory implementation ... posixselecting default "max_connections" ... 100selecting default "shared_buffers" ... 128MBselecting default time zone ... Asia/Shanghaicreating configuration files ... okrunning bootstrap script ... okperforming post-bootstrap initialization ... *** stack smashing detected ***: terminatedAborted (core dumped)child process exited with exit code 134initdb: 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='clang -fno-stack-protector'
However, the problem still exists. Is there anyone else having this issue?
Regards,
Haorong Xu
