Re: BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault

From: Chris Bandy <chris(dot)bandy(at)crunchydata(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault
Date: 2019-12-03 23:05:26
Message-ID: 08312668-6aa1-e786-8dd2-7bfd91eaf47c@crunchydata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 12/3/19 3:33 PM, Chris Bandy wrote:
> Hello,
>
> I am able to reproduce this on macOS 10.14 (Mojave) in multiple versions
> of Ruby and in a minimal C program.
>
I was also able to reproduce this with the attached Python program and
psycopg2 package.

Steps to reproduce:

1. Install libpq for PostgreSQL 12:
brew install postgresql(at)12

2. Install the psycopg2 package:
pip install psycopg2

3. Start a PostgreSQL server:
docker run --rm -d -p 127.0.0.1:5432:5432 postgres:12

4. Execute some GSS path before and after fork:
python macos-gss-crash.py

It generates a crash report and prints:

main ok
-11

In this and the previous tests I can avoid/workaround the segfault by
specifying gssencmode=disable.

Thanks!

Chris

Attachment Content-Type Size
macos-gss-crash.py text/x-python-script 301 bytes
Python_2019-12-03-165203.crash text/plain 47.1 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephen Frost 2019-12-03 23:31:32 Re: BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault
Previous Message Chris Bandy 2019-12-03 21:33:28 Re: BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) - Segmentation fault