Thread: git head crash/regression failures
I am seeing psql crash and massive regression test failures in git head.
The psql crash happens if .psqlrc contains:
\set COMP_KEYWORD_CASE upper
and the crash backtrace is:
Program received signal SIGSEGV, Segmentation fault.
0x000055555557f350 in slash_yylex (yylval_param=yylval_param@entry=0x0, yyscanner=0x5555555fb6c0) at
psqlscanslash.c:1325
1325 *yy_cp = yyg->yy_hold_char;
(gdb) bt
#0 0x000055555557f350 in slash_yylex (yylval_param=yylval_param@entry=0x0, yyscanner=0x5555555fb6c0) at
psqlscanslash.c:1325
#1 0x00005555555806a2 in psql_scan_slash_command (state=state@entry=0x5555555f8b20) at psqlscanslash.l:510
#2 0x00005555555689b0 in HandleSlashCmds (scan_state=scan_state@entry=0x5555555f8b20,
cstack=cstack@entry=0x5555555fb760,query_buf=0x5555555fb780,
previous_buf=0x5555555fb8b0) at command.c:212
#3 0x000055555557e3c9 in MainLoop (source=source@entry=0x5555555fb490) at mainloop.c:486
#4 0x00005555555670ed in process_file (filename=0x7fffffffda10 "/var/lib/postgresql/.psqlrc",
use_relative_path=<optimizedout>) at command.c:3594
#5 0x0000555555584a1e in process_psqlrc_file (filename=0x7fffffffda10 "/var/lib/postgresql/.psqlrc") at
startup.c:781
#6 0x0000555555584b71 in process_psqlrc (argv0=<optimized out>) at startup.c:756
#7 0x0000555555585adc in main (argc=<optimized out>, argv=0x7fffffffe418) at startup.c:315
The regression test seem to be crashing from \d. For example, in
src/test/regress/results/tablespace.out, once this line appears:
\d testschema.test_index1
the file ends, while the expected file has many more lines.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
On 2019-Mar-28, Bruce Momjian wrote: > I am seeing psql crash and massive regression test failures in git head. > The psql crash happens if .psqlrc contains: > > \set COMP_KEYWORD_CASE upper > > and the crash backtrace is: > > Program received signal SIGSEGV, Segmentation fault. > 0x000055555557f350 in slash_yylex (yylval_param=yylval_param@entry=0x0, yyscanner=0x5555555fb6c0) at psqlscanslash.c:1325 > 1325 *yy_cp = yyg->yy_hold_char; > (gdb) bt > #0 0x000055555557f350 in slash_yylex (yylval_param=yylval_param@entry=0x0, yyscanner=0x5555555fb6c0) at psqlscanslash.c:1325 > #1 0x00005555555806a2 in psql_scan_slash_command (state=state@entry=0x5555555f8b20) at psqlscanslash.l:510 Did you try "make maintainer-clean"? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On Thu, Mar 28, 2019 at 12:10:23PM -0300, Alvaro Herrera wrote: > On 2019-Mar-28, Bruce Momjian wrote: > > > I am seeing psql crash and massive regression test failures in git head. > > The psql crash happens if .psqlrc contains: > > > > \set COMP_KEYWORD_CASE upper > > > > and the crash backtrace is: > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x000055555557f350 in slash_yylex (yylval_param=yylval_param@entry=0x0, yyscanner=0x5555555fb6c0) at psqlscanslash.c:1325 > > 1325 *yy_cp = yyg->yy_hold_char; > > (gdb) bt > > #0 0x000055555557f350 in slash_yylex (yylval_param=yylval_param@entry=0x0, yyscanner=0x5555555fb6c0) at psqlscanslash.c:1325 > > #1 0x00005555555806a2 in psql_scan_slash_command (state=state@entry=0x5555555f8b20) at psqlscanslash.l:510 > > Did you try "make maintainer-clean"? Wow, that fixed it. I thought my work flow didn't require that, but obviously it does. Thanks so much. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +