public inbox for [email protected]
help / color / mirror / Atom feedFrom: Kashif Zeeshan <[email protected]>
To: Xu Haorong <[email protected]>
To: Postgres General <[email protected]>
Subject: Re: Stack Smashing Detected When Executing initdb
Date: Sun, 23 Jun 2024 19:13:40 +0500
Message-ID: <CAAPsdhcWjTmYgURcO8VHpHh+ypNPS-GRs+zYAZ4oviWuSeXW6A@mail.gmail.com> (raw)
In-Reply-To: <TYZPR04MB8178D6AFD6CBC03F11F051C6F7CB2@TYZPR04MB8178.apcprd04.prod.outlook.com>
References: <TYZPR04MB81783A90E99EEE85978FF705F7CB2@TYZPR04MB8178.apcprd04.prod.outlook.com>
<CAAPsdhcxrEBfU8oKsFZ5ybYfPGBMuV==pR-q_XazaUqhq-Acgg@mail.gmail.com>
<TYZPR04MB8178D6AFD6CBC03F11F051C6F7CB2@TYZPR04MB8178.apcprd04.prod.outlook.com>
Hi Xu
You need to enable some settings for the code dump to generated.
For the settings you can use following link.
https://access.redhat.com/solutions/4896
Regards
Kashif Zeeshan
On Sun, Jun 23, 2024 at 7:07 PM Xu Haorong <[email protected]> wrote:
> Hi Zeeshan,
>
> Thank you for helping me. I tried to analyze the core dump file, but
> unfortunately it didn't seem to have generated one. Therefore I ran initdb
> with gdb, which produced following output:
>
> Program received signal SIGPIPE, Broken pipe.
> 0x00007ffff791c574 in __GI___libc_write (fd=4, buf=0x555555636a60,
> nbytes=64) at ../sysdeps/unix/sysv/linux/write.c:26
> warning: 26 ../sysdeps/unix/sysv/linux/write.c: No such file or directory
>
> The error message clearly indicates that something like write.c is
> missing, which is included in GNU C Library. However, I found that I've
> already installed it on my computer. It also confuses me that there was no
> core dump file at all, since initdb says "Aborted (core dumped)". I'd
> really appreciate if you can give me further information.
>
> Regards,
> Haorong Xu
> ------------------------------
> *发件人:* Kashif Zeeshan <[email protected]>
> *发送时间:* 2024年6月23日 16:50
> *收件人:* Xu Haorong <[email protected]>
> *抄送:* [email protected] <[email protected]>
> *主题:* Re: Stack Smashing Detected When Executing initdb
>
> 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 <[email protected]>
> 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='clang -fno-stack-protector'*
>
> However, the problem still exists. Is there anyone else having this issue?
>
> Regards,
> Haorong Xu
>
>
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Stack Smashing Detected When Executing initdb
In-Reply-To: <CAAPsdhcWjTmYgURcO8VHpHh+ypNPS-GRs+zYAZ4oviWuSeXW6A@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox