Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kb2vv-0003Ri-MR for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Nov 2020 14:41:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kb2vu-0003XF-Lf for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Nov 2020 14:41:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kb2vu-0003X8-Fm for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2020 14:41:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kb2vs-0001sb-FF for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2020 14:41:42 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0A6Efaar1570030; Fri, 6 Nov 2020 09:41:36 -0500 From: Tom Lane To: Raphael Megzari cc: PostgreSQL mailing lists , Pavel Stehule , Thomas Munro Subject: Re: BUG #16665: Segmentation fault In-reply-to: <6931c615-6550-4aec-aaf2-7dd9dae30d2a@Canary> References: <16665-aaf4e1def393c340@postgresql.org> <5d0420e9-2935-439b-a4a2-543b59c2d8c1@Canary> <536d9e75-1652-43a7-b855-3768511b2b88@Canary> <3e1a2c52-6b71-4f30-adca-08f09a6b3b49@Canary> <116721f8-32b1-4b1b-9023-01e2510bdf55@Canary> <16aeb6fe-a202-461e-ae0b-16bf65f17e0b@Canary> <3436617.1602599359@sss.pgh.pa.us> <6931c615-6550-4aec-aaf2-7dd9dae30d2a@Canary> Comments: In-reply-to Raphael Megzari message dated "Fri, 06 Nov 2020 11:51:46 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1570028.1604673696.1@sss.pgh.pa.us> Date: Fri, 06 Nov 2020 09:41:36 -0500 Message-ID: <1570029.1604673696@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Raphael Megzari writes: > I have two questions > - How can I make sure to have a postgres that includes debugging symbols? (1) install the associated debug symbols package, or (2) build from source and use --enable-debug configure option. > - How can I verify after that my version includes debugging symbols? You could attach to a running backend process with gdb and see whether "bt full" gives you more than minimal output. regards, tom lane