pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: wobbet@wobbet.com, Robert Sanford <wobbet@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Segmentation Fault
Date: Wed, 13 Sep 2023 19:58:57 -0400
Message-ID: <3030992.1694649537@sss.pgh.pa.us> (raw)
In-Reply-To: <CABa+nRuatSjnqsPfnoo0APzgeM1Um94FesYj6H1YKB1qJ8JoqA@mail.gmail.com>
References: <CABa+nRvwZy_5t1QF9NJNGwAf03tv_PO_Sg1FsN1+-3Odb1XgBA@mail.gmail.com>
	<CABa+nRuatSjnqsPfnoo0APzgeM1Um94FesYj6H1YKB1qJ8JoqA@mail.gmail.com>

Robert Sanford <wobbet@gmail.com> writes:
> I realized that when I was running GDB I just took a snap of when it
> failed. Here I've added after continuing and requesting a backtrace.

This is still quite unhelpful; it appears to show normal behavior in
a process that's not the failing one.  There is some advice about
collecting useful backtraces at

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

I'd counsel the method of enabling core dumps and then attaching
gdb to a core file, rather than dealing with live processes.

			regards, tom lane





view thread (10+ messages)  latest in thread

Message-ID: <3030992.1694649537@sss.pgh.pa.us>
Permalink:  ../3030992.1694649537@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3030992.1694649537@sss.pgh.pa.us

 · 

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: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, wobbet@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: Segmentation Fault
  In-Reply-To: <3030992.1694649537@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox