Re: Segfault behaviour

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Азат Якупов <azat_yakupov(at)inbox(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Segfault behaviour
Date: 2019-04-21 19:46:18
Message-ID: 17224.1555875978@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?utf-8?B?0JDQt9Cw0YIg0K/QutGD0L/QvtCy?= <azat_yakupov(at)inbox(dot)ru> writes:
> A few days ago I faced with an error on OS level but unfortunately I didn’t find any error in PostgreSQL log file (just notification then PostgreSQL process has been shutdown).
> The PostgreSQL version is "PostgreSQL 11.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36), 64-bit"

> The error looks like below

> postmaster[34176]: segfault at 7f9954573ff8 ip 00007fbfc13e3756 sp 00007ffd5b17c198 error 4 in libc-2.17.so[7fbfc128e000+1c2000]

I agree that looks like a bug, but we can't do anything at all with
so little information to go on. Please see here for info on
filing useful bug reports:

https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-04-22 01:50:51 Re: Possible to store invalid SCRAM-SHA-256 Passwords
Previous Message Азат Якупов 2019-04-21 18:47:58 Segfault behaviour