BUG #18364: psql execution error: Segmentation fault

Started by PG Bug reporting formabout 2 years ago2 messagesbugs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following bug has been logged on the website:

Bug reference: 18364
Logged by: George Gustavo Mirocha
Email address: gmirocha@gmail.com
PostgreSQL version: 16.2
Operating system: RHEL 8 & CENTOS 7
Description:

After upgrade Postgresql from 16.1 to 16.2 in both CENTOS 7 and RHEL 8 I'm
getting the segmentation fault error when I try to execute any "\" command
on psql. I have got this error in different hosts, plataforms, etc.

-bash-4.2$ psql
psql (16.2)
Type "help" for help.

postgres=# \l
Segmentation fault

------------- Execution with DEBUG:
postgres=# \l

Program received signal SIGSEGV, Segmentation fault.
slash_yylex (yylval_param=yylval_param@entry=0x0, yyscanner=0x6e2300) at
psqlscanslash.c:1312
1312 *yy_cp = yyg->yy_hold_char;
(gdb)

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: PG Bug reporting form (#1)
Re: BUG #18364: psql execution error: Segmentation fault

PG Bug reporting form <noreply@postgresql.org> writes:

After upgrade Postgresql from 16.1 to 16.2 in both CENTOS 7 and RHEL 8 I'm
getting the segmentation fault error when I try to execute any "\" command
on psql. I have got this error in different hosts, plataforms, etc.

Given the location of the error, it seems like you might have a
problem with inconsistent ABI for "flex". I'm not quite sure
how you'd get there, because that's usually pretty self-contained.
(Once there was a "libfl.a" that could possibly cause this sort of
problem, but I don't think that exists in modern flex versions.)
Anyway, I'd check that you have a consistent installation of flex
and then rebuild Postgres from source.

regards, tom lane