Hi Wen, On Wed, Jul 26, 2023 at 7:55 PM Wen Yi <wen...@qq.com> wrote: ... snip ... > ----- Backtrace ----- > corrupted double-linked list > > > Fatal signal: Aborted > ----- Backtrace ----- > done > server started > 0x5557bf5908b0 ??? ... snip ... > --------------------- > A fatal error internal to GDB has been detected, further > debugging is not possible. GDB will now terminate. > > This is a bug, please report it. For instructions, see: > <https://www.gnu.org/software/gdb/bugs/>. > > Aborted (core dumped) > [postgres@fedora postgres]$ > > -------------------------------------------------------------------------------------------------------------- > > As you can see, the gdb tell me I should report this, because gdb think > there's a double-free. > But I check the postgres, it keep the run rightly, like this:(Before I run > the psql, I print the log file) >
I think you hit a gdb bug. The error message from gdb references https://www.gnu.org/software/gdb/bugs/ which has instructions on reporting bugs about gdb. > 2023-07-26 22:16:17.489 CST [83554] LOG: database system is ready to accept > connections > [postgres@fedora postgres]$ psql > psql (17devel) > Type "help" for help. > > postgres=# \q > [postgres@fedora postgres]$ I guess gdb hit this bug after detaching from the backend you were debugging. So it continued running. In case it crashed because something went wrong. postmaster will just restart all the backends and will allow you to reconnect. -- Best Wishes, Ashutosh Bapat
